Systems and methods for optimizing storage and retention of deduplicated secondary copies at storage platforms that are write-once read-many (worm) enabled

ABSTRACT

A data storage management system is enhanced to accommodate, and moreover to optimize, the storing and retention of deduplicated secondary copies at write-once read-many (WORM) enabled storage platforms. Enhancements include without limitation: user interface (UI) options to enable WORM functionality for secondary storage, whether used for deduplicated or non-deduplicated secondary copies; enhancements to secondary copy (e.g., deduplication copy, backup) operations; and pruning changes. The storage manager is generally responsible for managing the creation, tracking, and deletion of secondary copies, with and without deduplication. Media agents that store secondary copies to and prune them from the WORM-enabled storage platforms also are enhanced for communicating and interoperating with both bucket-level and object-level WORM-enabled storage platforms to implement the features disclosed herein.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application claims the benefit of priority to U.S. Provisional Pat. App. No. 63/278,015, which was filed on Nov. 10, 2021 with the title of: “Systems And Methods For Optimizing Storage And Retention Of Deduplicated Secondary Copies At Storage Platforms That Are Write-Once Read-Many (WORM) Enabled,” and which is incorporated by reference in its entirety herein. Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference in their entireties under 37 CFR 1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document and/or the patent disclosure as it appears in the United States Patent and Trademark Office patent file and/or records, but otherwise reserves all copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seek reliable, cost-effective ways to protect the information stored on their computer networks while minimizing impact on productivity. A company might back up critical computing systems such as databases, file servers, web servers, virtual machines, and so on as part of a routine schedule. Because of the rise in ransomware attacks, protecting data in an environment that is free from the risk of data modifications has become increasingly important. Accordingly, storage platforms, such as storage arrays and cloud-based storage, now offer “write-once read-many” (WORM) storage technologies that securely protect stored data in its originally written form for a specified time. The specified time is referred to herein as the “WORM lock retention period” or “WORM hold” or “WORM lock”. During WORM lock, data stored on the storage platform is safe from the risk of ransomware-induced changes, such as encryption. Because the WORM lock is the responsibility of and enforced by the storage platform, the data cannot be changed or deleted by external systems or by mistakes of human intervention. Thus, WORM-enabled storage has become a desirable choice for saving secondary copies (e.g., backup copies, archive copies, reference copies, etc.). WORM-enabled storage is implemented in a variety of cloud storage services and in non-cloud data center storage arrays, such as those offered by NetApp, Inc. and by Dell EMC.

However, deduplicated secondary copies do not readily fit within the usage patterns of WORM-enabled storage, because deduplicated data relies on the persistence of older reference data. Thus, WORM locking deduplicated data introduces some undesirable side-effects, such as having to hold original reference data for much longer than desired on the possibility that later deduplicated data will need to reference the earlier data.

SUMMARY

The present inventors devised enhancements to a data storage management system that enable the system to accommodate, and moreover to optimize, the storing and retention of deduplicated secondary copies at WORM-enabled storage platforms. This technological improvement enables users to securely control and configure, via the enhanced data storage management system, how the WORM-enabled storage platform will handle the secondary copies generated by the system. The system, via an improved user interface, natively intakes configuration and/or administrative inputs for setting up secondary copy jobs targeted to WORM-enabled storage, and sets up data storage destinations (so-called “buckets”) and WORM retention parameters at the WORM-enabled storage platforms.

Additionally, the data storage management system is further enhanced to interoperate with either bucket-level or object-level WORM features of different storage platforms. Some storage platforms provide so-called “bucket-level” WORM storage in which a selected WORM lock duration (e.g., 60 days) is added to the creation time of every new data object created in the bucket (e.g., data folder, data file, etc.). In bucket-level WORM, the WORM lock duration is fixed and applies to every object in the bucket starting with the object's creation time. Some storage platforms provide so-called “object-level” WORM, in which a selected point in time (e.g., midnight of December 31st) may be chosen or implemented as the time at which the WORM lock is released for an object in the bucket, independently of the release time of another object. These two approaches to how storage platforms apply and enforce WORM locks affect how the illustrative data storage management system configures storage and retention policies for secondary copies, how much storage it allocates to buckets at the storage platform, and how it handles internal system resources and operational schemes to optimize the storage, retention, and deletion of deduplicated secondary copies generated by the system.

The system illustratively relies on periodically sealing or closing its deduplication database (DDB), which is an internal system resource that stores unique signatures of data blocks being backed up. The DDB is used in making deduplicated secondary copies. After a DDB is sealed, it is no longer used for subsequent secondary copy jobs and instead, a new DDB is created and used as the active DDB of the system. The sealed DDB may be discarded as soon as the system finds it convenient. By sealing the active DDB relatively frequently, the system modulates how much WORM-enabled storage it needs, and for how long, for its deduplicated secondary copies. Illustratively, for a storage policy that specifies a certain retention period for deduplicated secondary copies, e.g., 30 days, the system assigns an equal number of days to the DDB sealing frequency. The WORM lock is then configured to a value based on the retention period and the DDB sealing frequency. Certain enhancements are disclosed herein for optimizing how soon the system may prune deduplicated secondary copies that have met their retention period after the DDB is sealed.

For bucket-level WORM storage, the system defines the WORM lock duration as the sum of the retention period and the DDB sealing frequency, e.g., 30 days+30 days=60 days, without limitation. In a traditional prior-art system, this would mean that the last job executed on the last (30th) day of the DDB sealing cycle will be locked for 60 days, i.e., 90 days from the day that the first job was executed on the first day of the DDB sealing cycle. Whereas the prior art solution averaged 75 days of data storage when using the example parameters above, the enhancements disclosed for bucket-level WORM storage reduce the average stay of copies to 60 days, which is a substantial reduction. Shorter stays require less total storage capacity and lower costs for cloud storage.

For object-level WORM storage, the system defines the WORM lock expiry as a fixed point in time, based on summing the retention period and the DDB sealing frequency, e.g., 60 days from DDB creation, without limitation. This means that, after the active DDB is sealed and no longer needed, each deduplicated secondary copy is no longer needed after its retention period expires and it becomes eligible for pruning. Thus, the first job executed on the first day of the DDB sealing cycle is eligible for pruning on day 60, whereas the last job executed on the last day of the DDB sealing cycle (e.g., on day 30) only needs 30 more days of retention and thus is also eligible for pruning on day 60. Thus, the WORM lock duration is variable across the various secondary copies in the bucket so that it is lifted at the same point in time. With object-level WORM enablement, the storage platform releases its WORM lock on all deduplicated secondary copies associated with the sealed DDB at (substantially) the same time, thus making the deduplicated secondary copies eligible to be pruned. Using the example parameters above, the enhancements disclosed for object-level WORM storage result in an average data storage time of 45 days, much less than the prior art average of 75 days and also substantially less than the enhancements disclosed for bucket-level WORM storage averaging 60 days. The storage time also affects the amount of storage that needs to be provisioned. For the same amount of data in a set of deduplicated secondary copies associated with a given DDB, bucket-level storage averages to longer hold times and thus the bucket must be provisioned to a larger size than a comparable bucket for object-level WORM enablement.

A WORM-enabled storage platform as referenced herein may be implemented in a cloud computing environment or in a non-cloud data center using storage arrays or other data storage devices, without limitation. Enhancements include without limitation: user interface (UI) options to enable WORM functionality for secondary storage, whether used for deduplicated or non-deduplicated secondary copies; enhancements to secondary copy operations; and pruning changes. A storage manager computing device is generally responsible for managing the creation, tracking, and deletion of secondary copies, with and without deduplication. Media agents that store secondary copies to, and prune them from, the WORM-enabled storage platforms also are enhanced for communicating and interoperating with both bucket-level and object-level WORM-enabled storage platforms to implement the features disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an example information management system.

FIG. 1B is a detailed view of a primary storage device, a secondary storage device, and some examples of primary data and secondary copy data.

FIG. 1C is a block diagram of an example information management system including a storage manager, one or more data agents, and one or more media agents.

FIG. 1D is a block diagram illustrating a scalable information management system.

FIG. 1E illustrates certain secondary copy operations according to an example storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structures that may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primary data to a destination such as a failover site using secondary copy data.

FIG. 2B illustrates an information management system architecture incorporating use of a network file system (NFS) protocol for communicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable managed data pool architecture.

FIGS. 3A-3B depict block diagrams illustrating some salient portions of a system 300 for optimizing the storing and retention of deduplicated secondary copies at storage platforms that are bucket-level write-once read-many (WORM) enabled, according to an illustrative embodiment.

FIG. 3C is a block diagram illustrating how system 300 organizes deduplicated secondary copies in volume folders in a bucket at a WORM-enabled storage platform, according to an illustrative embodiment.

FIGS. 4A-4B depict block diagrams illustrating portions of system 300 configured for optimizing the storing and retention of deduplicated secondary copies at storage platforms that are object-level WORM-enabled, according to an illustrative embodiment.

FIG. 5A depicts bucket-level WORM handling of deduplicated secondary copies according to an example in the prior art.

FIG. 5B depicts bucket-level WORM handling of deduplicated secondary copies in system 300, according to an illustrative embodiment.

FIG. 5C depicts object-level WORM handling of deduplicated secondary copies in system 300, according to an illustrative embodiment.

FIG. 6 depicts some salient operations of a method 600 according to an illustrative embodiment.

FIG. 7 depicts some salient operations of block 602 in method 600 according to an illustrative embodiment.

FIG. 8 depicts some salient operations of block 604 in method 600 according to an illustrative embodiment.

FIG. 9 depicts some salient operations of block 606B (bucket-level WORM) in method 600 according to an illustrative embodiment.

FIG. 10 depicts some salient operations of block 606O (object-level WORM) in method 600 according to an illustrative embodiment.

FIG. 11 depicts some salient operations of block 608 in method 600 according to an illustrative embodiment.

FIG. 12 depicts some salient operations of block 610 in method 600 according to an illustrative embodiment.

FIG. 13 is a block diagram illustrating some functional components of and/or associated with storage manager 340 in system 300, according to an illustrative embodiment.

FIG. 14 depicts example screenshot segments from the native user interface presented by system 300.

DETAILED DESCRIPTION

Detailed descriptions and examples of systems and methods according to one or more illustrative embodiments of the present invention may be found in the section entitled SYSTEMS AND METHODS FOR OPTIMIZING STORAGE AND RETENTION OF DEDUPLICATED SECONDARY COPIES AT STORAGE PLATFORMS THAT ARE WRITE-ONCE READ-MANY (WORM) ENABLED, as well as in the section entitled Example Embodiments, and also in FIGS. 3A-4B and 5B-14 herein. Furthermore, components and functionality for optimizing storage and retention of deduplicated secondary copies at storage platforms that are WORM enabled may be configured and/or incorporated into information management systems such as those described herein in FIGS. 1A-1H, 2A-2C, and 5A.

Various embodiments described herein are intimately tied to, enabled by, and would not exist except for, computer technology. For example, deduplication, DDB sealing, pruning, WORM-related calculations, and WORM settings described herein in reference to various embodiments cannot reasonably be performed by humans alone, without the computer technology upon which they are implemented.

Information Management System Overview

With the increasing importance of protecting and leveraging data, organizations simply cannot risk losing critical data. Moreover, runaway data growth and other modern realities make protecting and managing data increasingly difficult. There is therefore a need for efficient, powerful, and user-friendly solutions for protecting and managing data and for smart and efficient management of data storage. Depending on the size of the organization, there may be many data production sources which are under the purview of tens, hundreds, or even thousands of individuals. In the past, individuals were sometimes responsible for managing and protecting their own data, and a patchwork of hardware and software point solutions may have been used in any given organization. These solutions were often provided by different vendors and had limited or no interoperability. Certain embodiments described herein address these and other shortcomings of prior approaches by implementing scalable, unified, organization-wide information management, including data storage management.

FIG. 1A shows one such information management system 100 (or “system 100”), which generally includes combinations of hardware and software configured to protect and manage data and metadata that are generated and used by computing devices in system 100. System 100 may be referred to in some embodiments as a “storage management system” or a “data storage management system.” System 100 performs information management operations, some of which may be referred to as “storage operations” or “data storage operations,” to protect and manage the data residing in and/or managed by system 100. The organization that employs system 100 may be a corporation or other business entity, non-profit organization, educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may be compatible with and/or provide some or all of the functionality of the systems and corresponding components described in one or more of the following U.S. patents/publications and patent applications assigned to Commvault Systems, Inc., each of which is hereby incorporated by reference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval         System Used in Conjunction With a Storage Area Network”;     -   U.S. Pat. No. 7,107,298, entitled “System And Method For         Archiving Objects In An Information Store”;     -   U.S. Pat. No. 7,246,207, entitled “System and Method for         Dynamically Performing Storage Operations in a Computer         Network”;     -   U.S. Pat. No. 7,315,923, entitled “System And Method For         Combining Data Streams In Pipelined Storage Operations In A         Storage Network”;     -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and         Methods for Providing a Unified View of Storage Information”;     -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and         Retrieval System”;     -   U.S. Pat. No. 7,529,782, entitled “System and Methods for         Performing a Snapshot and for Restoring Data”;     -   U.S. Pat. No. 7,617,262, entitled “System and Methods for         Monitoring Application Data in a Data Replication System”;     -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;     -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating         Data Classification”;     -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For         Stored Data Verification”;     -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline         Indexing of Content and Classifying Stored Data”;     -   U.S. Pat. No. 8,230,195, entitled “System And Method For         Performing Auxiliary Storage Operations”;     -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server         for a Cloud Storage Environment, Including Data Deduplication         and Data Management Across Multiple Cloud Storage Sites”;     -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For         Management Of Virtualization Data”;     -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based         Deduplication”;     -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single         Instancing”;     -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a         Networked Deduplicated Storage System”;     -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated         Storage System”;     -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote         Single Instance Data Management”;     -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for         Retaining and Using Data Block Signatures in Data Protection         Operations”;     -   U.S. Pat. No. 9,444,811, entitled “Using An Enhanced Data Agent         To Restore Backed Up Data Across Autonomous Storage Management         Systems”;     -   U.S. Pat. No. 9,633,033 entitled “High Availability Distributed         Deduplicated Storage System”;     -   U.S. Pat. No. 10,228,962 entitled “Live Synchronization and         Management of Virtual Machines across Computing and         Virtualization Platforms and Using Live Synchronization to         Support Disaster Recovery”;     -   U.S. Pat. No. 10,255,143 entitled “Deduplication Replication In         A Distributed Deduplication Data Storage System”     -   U.S. Pat. No. 10,592,145, entitled “Machine Learning-Based Data         Object Storage”;     -   U.S. Pat. No. 10,684,924 entitled “Data Restoration Operations         Based on Network Path Information”;     -   U.S. Patent Pub. No. 2006/0224846, entitled “System and Method         to Support Single Instance Storage Operations” now abandoned;     -   U.S. Patent Pub. No. 2016/0350391 entitled “Replication Using         Deduplicated Secondary Copy Data” now abandoned;     -   U.S. Patent Pub. No. 2017/0235647 entitled “Data Protection         Operations Based on Network Path Information” now abandoned; and     -   U.S. Patent Pub. No. 2019/0108341 entitled “Ransomware Detection         And Data Pruning Management”.

System 100 includes computing devices and computing technologies. For instance, system 100 can include one or more client computing devices 102 and secondary storage computing devices 106, as well as storage manager 140 or a host computing device for it. Computing devices can include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers, servers, and minicomputers. Other computing devices can include mobile or portable computing devices, such as one or more laptops, tablet computers, personal data assistants, mobile phones (such as smartphones), and other mobile or portable computing devices such as embedded computers, set top boxes, vehicle-mounted devices, wearable computers, etc. Servers can include mail servers, file servers, database servers, virtual machine servers, and web servers. Any given computing device comprises one or more processors (e.g., CPU and/or single-core or multi-core processors), as well as corresponding non-transitory computer memory (e.g., random-access memory (RAM)) for storing computer programs which are to be executed by the one or more processors. Other computer memory for mass storage of data may be packaged/configured with the computing device (e.g., an internal hard disk) and/or may be external and accessible by the computing device (e.g., network-attached storage, a storage array, etc.). In some cases, a computing device includes cloud computing resources, which may be implemented as virtual machines. For instance, one or more virtual machines may be provided to the organization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtual machine(s) running on a physical host computing device (or “host machine”) operated by the organization. As one example, the organization may use one virtual machine as a database server and another virtual machine as a mail server, both virtual machines operating on the same host machine. A Virtual machine (“VM”) is a software implementation of a computer that does not physically exist and is instead instantiated in an operating system of a physical computer (or host machine) to enable applications to execute within the VM's environment, i.e., a VM emulates a physical computer. AVM includes an operating system and associated virtual resources, such as computer memory and processor(s). A hypervisor operates between the VM and the hardware of the physical host machine and is generally responsible for creating and running the VMs. Hypervisors are also known in the art as virtual machine monitors or a virtual machine managers or “VMMs”, and may be implemented in software, firmware, and/or specialized hardware installed on the host machine. Examples of hypervisors include ESX Server, by VMware, Inc. of Palo Alto, Calif.; Microsoft Virtual Server and Microsoft Windows Server Hyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM by Oracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems, Santa Clara, Calif. The hypervisor provides resources to each virtual operating system such as a virtual processor, virtual memory, a virtual network device, and a virtual disk. Each virtual machine has one or more associated virtual disks. The hypervisor typically stores the data of virtual disks in files on the file system of the physical host machine, called virtual machine disk files (“VMDK” in VMware lingo) or virtual hard disk image files (in Microsoft lingo). For example, VMware's ESX Server provides the Virtual Machine File System (VMFS) for the storage of virtual machine disk files. A virtual machine reads data from and writes data to its virtual disk much the way that a physical machine reads data from and writes data to a physical disk. Examples of techniques for implementing information management in a cloud computing environment are described in U.S. Pat. No. 8,285,681. Examples of techniques for implementing information management in a virtualized computing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic data storage devices, generally used for mass storage of data, including, e.g., primary storage devices 104 and secondary storage devices 108. Storage devices can generally be of any suitable type including, without limitation, disk drives, storage arrays (e.g., storage-area network (SAN) and/or network-attached storage (NAS) technology), semiconductor memory (e.g., solid state storage devices), network attached storage (NAS) devices, tape libraries, or other magnetic, non-tape storage devices, optical media storage devices, combinations of the same, etc. In some embodiments, storage devices form part of a distributed file system. In some cases, storage devices are provided in a cloud storage environment (e.g., a private cloud or one operated by a third-party vendor), whether for primary data or secondary copies or both.

Depending on context, the term “information management system” can refer to generally all of the illustrated hardware and software components in FIG. 1C, or the term may refer to only a subset of the illustrated components. For instance, in some cases, system 100 generally refers to a combination of specialized components used to protect, move, manage, manipulate, analyze, and/or process data and metadata generated by client computing devices 102. However, system 100 in some cases does not include the underlying components that generate and/or store primary data 112, such as the client computing devices 102 themselves, and the primary storage devices 104. Likewise secondary storage devices 108 (e.g., a third-party provided cloud storage environment) may not be part of system 100. As an example, “information management system” or “storage management system” may sometimes refer to one or more of the following components, which will be described in further detail below: storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, each client computing device 102 having an operating system and at least one application 110 and one or more accompanying data agents executing thereon; and associated with one or more primary storage devices 104 storing primary data 112. Client computing device(s) 102 and primary storage devices 104 may generally be referred to in some cases as primary storage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to be protected and managed. As just one illustrative example, in a corporate environment such data sources can be employee workstations and company servers such as a mail server, a web server, a database server, a transaction server, or the like. In system 100, data generation sources include one or more client computing devices 102. A computing device that has a data agent 142 installed and operating on it is generally referred to as a “client computing device” 102, and may include any type of computing device, without limitation. A client computing device 102 may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100, which may represent a logical grouping of one or more data agents installed on a client computing device 102. Storage manager 140 recognizes a client as a component of system 100, and in some embodiments, may automatically create a client component the first time a data agent 142 is installed on a client computing device 102. Because data generated by executable component(s) 110 is tracked by the associated data agent 142 so that it may be properly protected in system 100, a client may be said to generate data and to store the generated data to primary storage, such as primary storage device 104. However, the terms “client” and “client computing device” as used herein do not imply that a client computing device 102 is necessarily configured in the client/server sense relative to another computing device such as a mail server, or that a client computing device 102 cannot be a server in its own right. As just a few examples, a client computing device 102 can be and/or include mail servers, file servers, database servers, virtual machine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executing thereon which generate and manipulate the data that is to be protected from loss and managed in system 100. Applications 110 generally facilitate the operations of an organization, and can include, without limitation, mail server applications (e.g., Microsoft Exchange Server), file system applications, mail client applications (e.g., Microsoft Exchange Client), database applications or database management systems (e.g., SQL, Oracle, SAP, Lotus Notes Database), word processing applications (e.g., Microsoft Word), spreadsheet applications, financial applications, presentation applications, graphics and/or video applications, browser applications, mobile applications, entertainment applications, and so on. Each application 110 may be accompanied by an application-specific data agent 142, though not all data agents 142 are application-specific or associated with only application. A file manager application, e.g., Microsoft Windows Explorer, may be considered an application 110 and may be accompanied by its own data agent 142. Client computing devices 102 can have at least one operating system (e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.) installed thereon, which may support or host one or more file systems and other applications 110. In some embodiments, a virtual machine that executes on a host client computing device 102 may be considered an application 110 and may be accompanied by a specific data agent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can be connected to one another via one or more electronic communication pathways 114. For example, a first communication pathway 114 may communicatively couple client computing device 102 and secondary storage computing device 106; a second communication pathway 114 may communicatively couple storage manager 140 and client computing device 102; and a third communication pathway 114 may communicatively couple storage manager 140 and secondary storage computing device 106, etc. (see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 can include one or more networks or other connection types including one or more of the following, without limitation: the Internet, a wide area network (WAN), a local area network (LAN), a Storage Area Network (SAN), a Fibre Channel (FC) connection, a Small Computer System Interface (SCSI) connection, a virtual private network (VPN), a token ring or TCP/IP based network, an intranet network, a point-to-point link, a cellular network, a wireless data transmission system, a two-way cable system, an interactive kiosk network, a satellite network, a broadband network, a baseband network, a neural network, a mesh network, an ad hoc network, other appropriate computer or telecommunications networks, combinations of the same or the like. Communication pathways 114 in some cases may also include application programming interfaces (APIs) including, e.g., cloud service provider APIs, virtual machine management APIs, and hosted service provider APIs. The underlying infrastructure of communication pathways 114 may be wired and/or wireless, analog and/or digital, or any combination thereof; and the facilities used may be private, public, third-party provided, or any combination thereof, without limitation.

A “subclient” is a logical grouping of all or part of a client's primary data 112. In general, a subclient may be defined according to how the subclient data is to be protected as a unit in system 100. For example, a subclient may be associated with a certain storage policy. A given client may thus comprise several subclients, each subclient associated with a different storage policy. For example, some files may form a first subclient that requires compression and deduplication and is associated with a first storage policy. Other files of the client may form a second subclient that requires a different retention schedule as well as encryption, and may be associated with a different, second storage policy. As a result, though the primary data may be generated by the same application 110 and may belong to one given client, portions of the data may be assigned to different subclients for distinct treatment by system 100. More detail on subclients is given in regard to storage policies below.

Primary Data and Example Primary Storage Devices

Primary data 112 is generally production data or “live” data generated by the operating system and/or applications 110 executing on client computing device 102. Primary data 112 is generally stored on primary storage device(s) 104 and is organized via a file system operating on the client computing device 102. Thus, client computing device(s) 102 and corresponding applications 110 may create, access, modify, write, delete, and otherwise use primary data 112. Primary data 112 is generally in the native format of the source application 110. Primary data 112 is an initial or first stored body of data generated by the source application 110. Primary data 112 in some cases is created substantially directly from data generated by the corresponding source application 110. It can be useful in performing certain tasks to organize primary data 112 into units of different granularities. In general, primary data 112 can include files, directories, file system volumes, data blocks, extents, or any other hierarchies or organizations of data objects. As used herein, a “data object” can refer to (i) any file that is currently addressable by a file system or that was previously addressable by the file system (e.g., an archive file), and/or to (ii) a subset of such a file (e.g., a data block, an extent, etc.). Primary data 112 may include structured data (e.g., database files), unstructured data (e.g., documents), and/or semi-structured data. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 to access and modify metadata within primary data 112. Metadata generally includes information about data objects and/or characteristics associated with the data objects. For simplicity herein, it is to be understood that, unless expressly stated otherwise, any reference to primary data 112 generally also includes its associated metadata, but references to metadata generally do not include the primary data. Metadata can include, without limitation, one or more of the following: the data owner (e.g., the client or user that generates the data), the last modified time (e.g., the time of the most recent modification of the data object), a data object name (e.g., a file name), a data object size (e.g., a number of bytes of data), information about the content (e.g., an indication as to the existence of a particular search term), user-supplied tags, to/from information for email (e.g., an email sender, recipient, etc.), creation date, file type (e.g., format or application type), last accessed time, application type (e.g., type of application that generated the data object), location/network (e.g., a current, past or future location of the data object and network pathways to/from the data object), geographic location (e.g., GPS coordinates), frequency of change (e.g., a period in which the data object is modified), business unit (e.g., a group or department that generates, manages or is otherwise associated with the data object), aging information (e.g., a schedule, such as a time period, in which the data object is migrated to secondary or long term storage), boot sectors, partition layouts, file location within a file folder directory structure, user permissions, owners, groups, access control lists (ACLs), system metadata (e.g., registry information), combinations of the same or other similar information related to the data object. In addition to metadata generated by or related to file systems and operating systems, some applications 110 and/or other components of system 100 maintain indices of metadata for data objects, e.g., metadata associated with individual email messages. The use of metadata to perform classification and other functions is described in greater detail below.

Primary storage devices 104 storing primary data 112 may be relatively fast and/or expensive technology (e.g., flash storage, a disk drive, a hard-disk storage array, solid state memory, etc.), typically to support high-performance live production environments. Primary data 112 may be highly changeable and/or may be intended for relatively short term retention (e.g., hours, days, or weeks). According to some embodiments, client computing device 102 can access primary data 112 stored in primary storage device 104 by making conventional file system calls via the operating system. Each client computing device 102 is generally associated with and/or in communication with one or more primary storage devices 104 storing corresponding primary data 112. A client computing device 102 is said to be associated with or in communication with a particular primary storage device 104 if it is capable of one or more of: routing and/or storing data (e.g., primary data 112) to the primary storage device 104, coordinating the routing and/or storing of data to the primary storage device 104, retrieving data from the primary storage device 104, coordinating the retrieval of data from the primary storage device 104, and modifying and/or deleting data in the primary storage device 104. Thus, a client computing device 102 may be said to access data stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases, each primary storage device 104 is dedicated to an associated client computing device 102, e.g., a local disk drive. In other cases, one or more primary storage devices 104 can be shared by multiple client computing devices 102, e.g., via a local network, in a cloud storage implementation, etc. As one example, primary storage device 104 can be a storage array shared by a group of client computing devices 102, such as EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may be hosted in some cases by an entity other than the organization that employs the other components of system 100. For instance, the hosted services may be provided by online service providers. Such service providers can provide social networking services, hosted email services, or hosted productivity applications or other hosted applications such as software-as-a-service (SaaS), platform-as-a-service (PaaS), application service providers (ASPs), cloud services, or other mechanisms for delivering functionality via a network. As it services users, each hosted service may generate additional data and metadata, which may be managed by system 100, e.g., as primary data 112. In some cases, the hosted services may be accessed using one of the applications 110. As an example, a hosted mail service may be accessed via browser running on a client computing device 102.

Secondary Copies and Example Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data 112. Or primary storage devices 104 can be damaged, lost, or otherwise corrupted. For recovery and/or regulatory compliance purposes, it is therefore useful to generate and maintain copies of primary data 112. Accordingly, system 100 includes one or more secondary storage computing devices 106 and one or more secondary storage devices 108 configured to create and store one or more secondary copies 116 of primary data 112 including its associated metadata. The secondary storage computing devices 106 and the secondary storage devices 108 may be referred to as secondary storage subsystem 118.

Secondary copies 116 can help in search and analysis efforts and meet other information management goals as well, such as: restoring data and/or metadata if an original version is lost (e.g., by deletion, corruption, or disaster); allowing point-in-time recovery; complying with regulatory data retention and electronic discovery (e-discovery) requirements; reducing utilized storage capacity in the production system and/or in secondary storage; facilitating organization and search of data; improving user access to data files across multiple computing devices and/or hosted services; and implementing data retention and pruning policies.

A secondary copy 116 can comprise a separate stored copy of data that is derived from one or more earlier-created stored copies (e.g., derived from primary data 112 or from another secondary copy 116). Secondary copies 116 can include point-in-time data, and may be intended for relatively long-term retention before some or all of the data is moved to other storage or discarded. In some cases, a secondary copy 116 may be in a different storage device than other previously stored copies; and/or may be remote from other previously stored copies. Secondary copies 116 can be stored in the same storage device as primary data 112. For example, a disk array capable of performing hardware snapshots stores primary data 112 and creates and stores hardware snapshots of the primary data 112 as secondary copies 116. Secondary copies 116 may be stored in relatively slow and/or lower cost storage (e.g., magnetic tape). A secondary copy 116 may be stored in a backup or archive format, or in some other format different from the native source application format or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116 (e.g., using a media agent 144), enabling users to browse and restore at a later time and further enabling the lifecycle management of the indexed data. After creation of a secondary copy 116 that represents certain primary data 112, a pointer or other location indicia (e.g., a stub) may be placed in primary data 112, or be otherwise associated with primary data 112, to indicate the current location of a particular secondary copy 116. Since an instance of a data object or metadata in primary data 112 may change over time as it is modified by application 110 (or hosted service or the operating system), system 100 may create and manage multiple secondary copies 116 of a particular data object or metadata, each copy representing the state of the data object in primary data 112 at a particular point in time. Moreover, since an instance of a data object in primary data 112 may eventually be deleted from primary storage device 104 and the file system, system 100 may continue to manage point-in-time representations of that data object, even though the instance in primary data 112 no longer exists. For virtual machines, the operating system and other applications 110 of client computing device(s) 102 may execute within or under the management of virtualization software (e.g., a VMM), and the primary storage device(s) 104 may comprise a virtual disk created on a physical storage device. System 100 may create secondary copies 116 of the files or other data objects in a virtual disk file and/or secondary copies 116 of the entire virtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data 112. First, secondary copies 116 can be stored in a different format from primary data 112 (e.g., backup, archive, or other non-native format). For this or other reasons, secondary copies 116 may not be directly usable by applications 110 or client computing device 102 (e.g., via standard system calls or otherwise) without modification, processing, or other intervention by system 100 which may be referred to as “restore” operations. Secondary copies 116 may have been processed by data agent 142 and/or media agent 144 in the course of being created (e.g., compression, deduplication, encryption, integrity markers, indexing, formatting, application-aware metadata, etc.), and thus secondary copy 116 may represent source primary data 112 without necessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device 108 that is inaccessible to application 110 running on client computing device 102 and/or hosted service. Some secondary copies 116 may be “offline copies,” in that they are not readily available (e.g., not mounted to tape or disk). Offline copies can include copies of data that system 100 can access without human intervention (e.g., tapes within an automated tape library, but not yet mounted in a drive), and copies that the system 100 can access only with some human intervention (e.g., tapes located at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—Secondary Storage Computing Devices

Creating secondary copies can be challenging when hundreds or thousands of client computing devices 102 continually generate large volumes of primary data 112 to be protected. Also, there can be significant overhead involved in the creation of secondary copies 116. Moreover, specialized programmed intelligence and/or hardware capability is generally needed for accessing and interacting with secondary storage devices 108. Client computing devices 102 may interact directly with a secondary storage device 108 to create secondary copies 116, but in view of the factors described above, this approach can negatively impact the ability of client computing device 102 to serve/service application 110 and produce primary data 112. Further, any given client computing device 102 may not be optimized for interaction with certain secondary storage devices 108.

Thus, system 100 may include one or more software and/or hardware components which generally act as intermediaries between client computing devices 102 (that generate primary data 112) and secondary storage devices 108 (that store secondary copies 116). In addition to off-loading certain responsibilities from client computing devices 102, these intermediate components provide other benefits. For instance, as discussed further below with respect to FIG. 1D, distributing some of the work involved in creating secondary copies 116 can enhance scalability and improve system performance. For instance, using specialized secondary storage computing devices 106 and media agents 144 for interfacing with secondary storage devices 108 and/or for performing certain data processing operations can greatly improve the speed with which system 100 performs information management operations and can also improve the capacity of the system to handle large numbers of such operations, while reducing the computational load on the production environment of client computing devices 102. The intermediate components can include one or more secondary storage computing devices 106 as shown in FIG. 1A and/or one or more media agents 144. Media agents are discussed further below (e.g., with respect to FIGS. 1C-1E). These special-purpose components of system 100 comprise specialized programmed intelligence and/or hardware capability for writing to, reading from, instructing, communicating with, or otherwise interacting with secondary storage devices 108.

Secondary storage computing device(s) 106 can comprise any of the computing devices described above, without limitation. In some cases, secondary storage computing device(s) 106 also include specialized hardware componentry and/or software intelligence (e.g., specialized interfaces) for interacting with certain secondary storage device(s) 108 with which they may be specially associated.

To create a secondary copy 116 involving the copying of data from primary storage subsystem 117 to secondary storage subsystem 118, client computing device 102 may communicate the primary data 112 to be copied (or a processed version thereof generated by a data agent 142) to the designated secondary storage computing device 106, via a communication pathway 114. Secondary storage computing device 106 in turn may further process and convey the data or a processed version thereof to secondary storage device 108. One or more secondary copies 116 may be created from existing secondary copies 116, such as in the case of an auxiliary copy operation, described further below.

Example Primary Data and an Example Secondary Copy

FIG. 1B is a detailed view of some specific examples of primary data stored on primary storage device(s) 104 and secondary copy data stored on secondary storage device(s) 108, with other components of the system removed for the purposes of illustration. Stored on primary storage device(s) 104 are primary data 112 objects including word processing documents 119A-B, spreadsheets 120, presentation documents 122, video files 124, image files 126, email mailboxes 128 (and corresponding email messages 129A-C), HTML/XML or other types of markup language files 130, databases 132 and corresponding tables or other data structures 133A-133C. Some or all primary data 112 objects are associated with corresponding metadata (e.g., “Meta1-11”), which may include file system metadata and/or application-specific metadata. Stored on the secondary storage device(s) 108 are secondary copy 116 data objects 134A-C which may include copies of or may otherwise represent corresponding primary data 112.

Secondary copy data objects 134A-C can individually represent more than one primary data object. For example, secondary copy data object 134A represents three separate primary data objects 133C, 122, and 129C (represented as 133C′, 122′, and 129C′, respectively, and accompanied by corresponding metadata Meta11, Meta3, and Meta8, respectively). Moreover, as indicated by the prime mark (′), secondary storage computing devices 106 or other components in secondary storage subsystem 118 may process the data received from primary storage subsystem 117 and store a secondary copy including a transformed and/or supplemented representation of a primary data object and/or metadata that is different from the original format, e.g., in a compressed, encrypted, deduplicated, or other modified format. For instance, secondary storage computing devices 106 can generate new metadata or other information based on said processing, and store the newly generated information along with the secondary copies. Secondary copy data object 1346 represents primary data objects 120, 1336, and 119A as 120′, 1336′, and 119A′, respectively, accompanied by corresponding metadata Meta2, Meta10, and Meta1, respectively. Also, secondary copy data object 134C represents primary data objects 133A, 1196, and 129A as 133A′, 1196′, and 129A′, respectively, accompanied by corresponding metadata Meta9, Meta5, and Meta6, respectively.

Example Information Management System Architecture

System 100 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment. There are critical design choices involved in specifying the functional responsibilities of the components and the role of each component in system 100. Such design choices can impact how system 100 performs and adapts to data growth and other changing circumstances. FIG. 1C shows a system 100 designed according to these considerations and includes: storage manager 140, one or more data agents 142 executing on client computing device(s) 102 and configured to process primary data 112, and one or more media agents 144 executing on one or more secondary storage computing devices 106 for performing tasks involving secondary storage devices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information manager that is configured to perform certain control functions and also to store certain critical information about system 100—hence storage manager 140 is said to manage system 100. As noted, the number of components in system 100 and the amount of data under management can be large. Managing the components and data is therefore a significant task, which can grow unpredictably as the number of components and data scale to meet the needs of the organization. For these and other reasons, according to certain embodiments, responsibility for controlling system 100, or at least a significant portion of that responsibility, is allocated to storage manager 140. Storage manager 140 can be adapted independently according to changing circumstances, without having to replace or re-design the remainder of the system. Moreover, a computing device for hosting and/or operating as storage manager 140 can be selected to best suit the functions and networking needs of storage manager 140. These and other advantages are described in further detail below and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hosted by a suitable computing device. In some embodiments, storage manager 140 is itself a computing device that performs the functions described herein. Storage manager 140 comprises or operates in conjunction with one or more associated data structures such as a dedicated database (e.g., management database 146), depending on the configuration. The storage manager 140 generally initiates, performs, coordinates, and/or controls storage and other information management operations performed by system 100, e.g., to protect and control primary data 112 and secondary copies 116. In general, storage manager 140 is said to manage system 100, which includes communicating with, instructing, and controlling in some circumstances components such as data agents 142 and media agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140 may communicate with, instruct, and/or control some or all elements of system 100, such as data agents 142 and media agents 144. In this manner, storage manager 140 manages the operation of various hardware and software components in system 100. In certain embodiments, control information originates from storage manager 140 and status as well as index reporting is transmitted to storage manager 140 by the managed components, whereas payload data and metadata are generally communicated between data agents 142 and media agents 144 (or otherwise between client computing device(s) 102 and secondary storage computing device(s) 106), e.g., at the direction of and under the management of storage manager 140. Control information can generally include parameters and instructions for carrying out information management operations, such as, without limitation, instructions to perform a task associated with an operation, timing information specifying when to initiate a task, data path information specifying what components to communicate with or access in carrying out an operation, and the like. In other embodiments, some information management operations are controlled or initiated by other components of system 100 (e.g., by media agents 144 or data agents 142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one or more of the following functions:

-   -   communicating with data agents 142 and media agents 144,         including transmitting instructions, messages, and/or queries,         as well as receiving status reports, index information,         messages, and/or queries, and responding to same;     -   initiating execution of information management operations;     -   initiating restore and recovery operations;     -   managing secondary storage devices 108 and inventory/capacity of         the same;     -   allocating secondary storage devices 108 for secondary copy         operations;     -   reporting, searching, and/or classification of data in system         100;     -   monitoring completion of and status reporting related to         information management operations and jobs;     -   tracking movement of data within system 100;     -   tracking age information relating to secondary copies 116,         secondary storage devices 108, comparing the age information         against retention guidelines, and initiating data pruning when         appropriate;     -   tracking logical associations between components in system 100;     -   protecting metadata associated with system 100, e.g., in         management database 146;     -   implementing job management, schedule management, event         management, alert management, reporting, job history         maintenance, user security management, disaster recovery         management, and/or user interfacing for system administrators         and/or end users of system 100;     -   sending, searching, and/or viewing of log files; and     -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storage manager database 146” or “management database 146”) of management-related data and information management policies 148. Database 146 is stored in computer memory accessible by storage manager 140. Database 146 may include a management index 150 (or “index 150”) or other data structure(s) that may store: logical associations between components of the system; user preferences and/or profiles (e.g., preferences regarding encryption, compression, or deduplication of primary data or secondary copies; preferences regarding the scheduling, type, or other aspects of secondary copy or other operations; mappings of particular information management users or user accounts to certain computing devices or other components, etc.; management tasks; media containerization; other useful data; and/or any combination thereof. For example, storage manager 140 may use index 150 to track logical associations between media agents 144 and secondary storage devices 108 and/or movement of data to/from secondary storage devices 108. For instance, index 150 may store data associating a client computing device 102 with a particular media agent 144 and/or secondary storage device 108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain information management operations on an individual basis. But while this may be acceptable for some recovery operations or other infrequent tasks, it is often not workable for implementing on-going organization-wide data protection and management. Thus, system 100 may utilize information management policies 148 for specifying and executing information management operations on an automated basis. Generally, an information management policy 148 can include a stored data structure or other information source that specifies parameters (e.g., criteria and rules) associated with storage management or other information management operations. Storage manager 140 can process an information management policy 148 and/or index 150 and, based on the results, identify an information management operation to perform, identify the appropriate components in system 100 to be involved in the operation (e.g., client computing devices 102 and corresponding data agents 142, secondary storage computing devices 106 and corresponding media agents 144, etc.), establish connections to those components and/or between those components, and/or instruct and control those components to carry out the operation. In this manner, system 100 can translate stored information into coordinated activity among the various computing devices in system 100.

Management database 146 may maintain information management policies 148 and associated data, although information management policies 148 can be stored in computer memory at any appropriate location outside management database 146. For instance, an information management policy 148 such as a storage policy may be stored as metadata in a media agent database 152 or in a secondary storage device 108 (e.g., as an archive copy) for use in restore or other information management operations, depending on the embodiment. Information management policies 148 are described further below. According to certain embodiments, management database 146 comprises a relational database (e.g., an SQL database) for tracking metadata, such as metadata associated with secondary copy operations (e.g., what client computing devices 102 and corresponding subclient data were protected and where the secondary copies are stored and which media agent 144 performed the storage operation(s)). This and other metadata may additionally be stored in other locations, such as at secondary storage computing device 106 or on the secondary storage device 108, allowing data recovery without the use of storage manager 140 in some cases. Thus, management database 146 may comprise data needed to kick off secondary copy operations (e.g., storage policies, schedule policies, etc.), status and reporting information about completed jobs (e.g., status and error reports on yesterday's backup jobs), and additional information sufficient to enable restore and disaster recovery operations (e.g., media agent associations, location indexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158, and a management agent 154, all of which may be implemented as interconnected software modules or application programs. These are described further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitors the status of some or all information management operations previously performed, currently being performed, or scheduled to be performed by system 100. A job is a logical grouping of information management operations such as daily storage operations scheduled for a certain set of subclients (e.g., generating incremental block-level backup copies 116 at a certain time every day for database files in a certain geographical location). Thus, jobs agent 156 may access information management policies 148 (e.g., in management database 146) to determine when, where, and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and display software, such as a graphical user interface (GUI), an application program interface (API), and/or other interactive interface(s) through which users and system processes can retrieve information about the status of information management operations or issue instructions to storage manager 140 and other components. Via user interface 158, users may issue instructions to the components in system 100 regarding performance of secondary copy and recovery operations. For example, a user may modify a schedule concerning the number of pending secondary copy operations. As another example, a user may employ the GUI to view the status of pending secondary copy jobs or to monitor the status of certain components in system 100 (e.g., the amount of capacity left in a storage device). Storage manager 140 may track information that permits it to select, designate, or otherwise identify content indices, deduplication databases, or similar databases or resources or data sets within its information management cell (or another cell) to be searched in response to certain queries. Such queries may be entered by the user by interacting with user interface 158.

Various embodiments of information management system 100 may be configured and/or designed to generate user interface data usable for rendering the various interactive user interfaces described. The user interface data may be used by system 100 and/or by another system, device, and/or software program (for example, a browser program), to render the interactive user interfaces. The interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays), consoles, etc., whether direct-connected to storage manager 140 or communicatively coupled remotely, e.g., via an internet connection. The present disclosure describes various embodiments of interactive and dynamic user interfaces, some of which may be generated by user interface agent 158, and which are the result of significant technological development. The user interfaces described herein may provide improved human-computer interactions, allowing for significant cognitive and ergonomic efficiencies and advantages over previous systems, including reduced mental workloads, improved decision-making, and the like. User interface 158 may operate in a single integrated view or console (not shown). The console may support a reporting capability for generating a variety of reports, which may be tailored to a particular aspect of information management.

User interfaces are not exclusive to storage manager 140 and in some embodiments a user may access information locally from a computing device component of system 100. For example, some information pertaining to installed data agents 142 and associated data streams may be available from client computing device 102. Likewise, some information pertaining to media agents 144 and associated data streams may be available from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability to communicate with other components within system 100 and/or with other information management cells via network protocols and application programming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST, virtualization software APIs, cloud service provider APIs, and hosted service provider APIs, without limitation. Management agent 154 also allows multiple information management cells to communicate with one another. For example, system 100 in some cases may be one information management cell in a network of multiple cells adjacent to one another or otherwise logically related, e.g., in a WAN or LAN. With this arrangement, the cells may communicate with one another through respective management agents 154. Inter-cell communications and hierarchy is described in greater detail in e.g., U.S. Pat. No. 7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”) may generally include a logical and/or physical grouping of a combination of hardware and software components associated with performing information management operations on electronic data, typically one storage manager 140 and at least one data agent 142 (executing on a client computing device 102) and at least one media agent 144 (executing on a secondary storage computing device 106). For instance, the components shown in FIG. 1C may together form an information management cell. Thus, in some configurations, a system 100 may be referred to as an information management cell or a storage operation cell. A given cell may be identified by the identity of its storage manager 140, which is generally responsible for managing the cell.

Multiple cells may be organized hierarchically, so that cells may inherit properties from hierarchically superior cells or be controlled by other cells in the hierarchy (automatically or otherwise). Alternatively, in some embodiments, cells may inherit or otherwise be associated with information management policies, preferences, information management operational parameters, or other properties or characteristics according to their relative position in a hierarchy of cells. Cells may also be organized hierarchically according to function, geography, architectural considerations, or other factors useful or desirable in performing information management operations. For example, a first cell may represent a geographic segment of an enterprise, such as a Chicago office, and a second cell may represent a different geographic segment, such as a New York City office. Other cells may represent departments within a particular office, e.g., human resources, finance, engineering, etc. Where delineated by function, a first cell may perform one or more first types of information management operations (e.g., one or more first types of secondary copies at a certain frequency), and a second cell may perform one or more second types of information management operations (e.g., one or more second types of secondary copies at a different frequency and under different retention rules). In general, the hierarchical information is maintained by one or more storage managers 140 that manage the respective cells (e.g., in corresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given client computing device 102, including operating systems, file systems, database applications, e-mail applications, and virtual machines, just to name a few. And, as part of the process of creating and restoring secondary copies 116, the client computing device 102 may be tasked with processing and preparing the primary data 112 generated by these various applications 110. Moreover, the nature of the processing/preparation can differ across application types, e.g., due to inherent structural, state, and formatting differences among applications 110 and/or the operating system of client computing device 102. Each data agent 142 is therefore advantageously configured in some embodiments to assist in the performance of information management operations based on the type of data that is being protected at a client-specific and/or application-specific level.

Data agent 142 is a component of information system 100 and is generally directed by storage manager 140 to participate in creating or restoring secondary copies 116. Data agent 142 may be a software program (e.g., in the form of a set of executable binary files) that executes on the same client computing device 102 as the associated application 110 that data agent 142 is configured to protect. Data agent 142 is generally responsible for managing, initiating, or otherwise assisting in the performance of information management operations in reference to its associated application(s) 110 and corresponding primary data 112 which is generated/accessed by the particular application(s) 110. For instance, data agent 142 may take part in copying, archiving, migrating, and/or replicating of certain primary data 112 stored in the primary storage device(s) 104. Data agent 142 may receive control information from storage manager 140, such as commands to transfer copies of data objects and/or metadata to one or more media agents 144. Data agent 142 also may compress, deduplicate, and encrypt certain primary data 112, as well as capture application-related metadata before transmitting the processed data to media agent 144. Data agent 142 also may receive instructions from storage manager 140 to restore (or assist in restoring) a secondary copy 116 from secondary storage device 108 to primary storage 104, such that the restored data may be properly accessed by application 110 in a suitable format as though it were primary data 112.

Each data agent 142 may be specialized for a particular application 110. For instance, different individual data agents 142 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows file system data, Microsoft Active Directory Objects data, SQL Server data, SharePoint data, Oracle database data, SAP database data, virtual machines and/or associated data, and other types of data. A file system data agent, for example, may handle data files and/or other file system information. If a client computing device 102 has two or more types of data 112, a specialized data agent 142 may be used for each data type. For example, to backup, migrate, and/or restore all of the data on a Microsoft Exchange server, the client computing device 102 may use: (1) a Microsoft Exchange Mailbox data agent 142 to back up the Exchange mailboxes; (2) a Microsoft Exchange Database data agent 142 to back up the Exchange databases; (3) a Microsoft Exchange Public Folder data agent 142 to back up the Exchange Public Folders; and (4) a Microsoft Windows File System data agent 142 to back up the file system of client computing device 102. In this example, these specialized data agents 142 are treated as four separate data agents 142 even though they operate on the same client computing device 102. Other examples may include archive management data agents such as a migration archiver or a compliance archiver, Quick Recovery® agents, and continuous data replication agents. Application-specific data agents 142 can provide improved performance as compared to generic agents. For instance, because application-specific data agents 142 may only handle data for a single software application, the design, operation, and performance of the data agent 142 can be streamlined. The data agent 142 may therefore execute faster and consume less persistent storage and/or operating memory than data agents designed to generically accommodate multiple different software applications 110.

Each data agent 142 may be configured to access data and/or metadata stored in the primary storage device(s) 104 associated with data agent 142 and its host client computing device 102, and process the data appropriately. For example, during a secondary copy operation, data agent 142 may arrange or assemble the data and metadata into one or more files having a certain format (e.g., a particular backup or archive format) before transferring the file(s) to a media agent 144 or other component. The file(s) may include a list of files or other metadata. In some embodiments, a data agent 142 may be distributed between client computing device 102 and storage manager 140 (and any other intermediate components) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 142. In addition, a data agent 142 may perform some functions provided by media agent 144. Other embodiments may employ one or more generic data agents 142 that can handle and process data from two or more different applications 110, or that can handle and process multiple data types, instead of or in addition to using specialized data agents 142. For example, one generic data agent 142 may be used to back up, migrate and restore Microsoft Exchange Mailbox data and Microsoft Exchange Database data, while another generic data agent may handle Microsoft Exchange Public Folder data and Microsoft Windows File System data.

Media Agents

As noted, off-loading certain responsibilities from client computing devices 102 to intermediate components such as secondary storage computing device(s) 106 and corresponding media agent(s) 144 can provide a number of benefits including improved performance of client computing device 102, faster and more reliable information management operations, and enhanced scalability. In one example which will be discussed further below, media agent 144 can act as a local cache of recently-copied data and/or metadata stored to secondary storage device(s) 108, thus improving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directed by storage manager 140 in creating and restoring secondary copies 116. Whereas storage manager 140 generally manages system 100 as a whole, media agent 144 provides a portal to certain secondary storage devices 108, such as by having specialized features for communicating with and accessing certain associated secondary storage device 108. Media agent 144 may be a software program (e.g., in the form of a set of executable binary files) that executes on a secondary storage computing device 106. Media agent 144 generally manages, coordinates, and facilitates the transmission of data between a data agent 142 (executing on client computing device 102) and secondary storage device(s) 108 associated with media agent 144. For instance, other components in the system may interact with media agent 144 to gain access to data stored on associated secondary storage device(s) 108, (e.g., to browse, read, write, modify, delete, or restore data). Moreover, media agents 144 can generate and store information relating to characteristics of the stored data and/or metadata, or can generate and store other types of information that generally provides insight into the contents of the secondary storage devices 108—generally referred to as indexing of the stored secondary copies 116. Each media agent 144 may operate on a dedicated secondary storage computing device 106, while in other embodiments a plurality of media agents 144 may operate on the same secondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storage device 108 if that media agent 144 is capable of one or more of: routing and/or storing data to the particular secondary storage device 108; coordinating the routing and/or storing of data to the particular secondary storage device 108; retrieving data from the particular secondary storage device 108; coordinating the retrieval of data from the particular secondary storage device 108; and modifying and/or deleting data retrieved from the particular secondary storage device 108. Media agent 144 in certain embodiments is physically separate from the associated secondary storage device 108. For instance, a media agent 144 may operate on a secondary storage computing device 106 in a distinct housing, package, and/or location from the associated secondary storage device 108. In one example, a media agent 144 operates on a first server computer and is in communication with a secondary storage device(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device 108 may instruct secondary storage device 108 to perform an information management task. For instance, a media agent 144 may instruct a tape library to use a robotic arm or other retrieval means to load or eject a certain storage media, and to subsequently archive, migrate, or retrieve data to or from that media, e.g., for the purpose of restoring data to a client computing device 102. As another example, a secondary storage device 108 may include an array of hard disk drives or solid state drives organized in a RAID configuration, and media agent 144 may forward a logical unit number (LUN) and other appropriate information to the array, which uses the received information to execute the desired secondary copy operation. Media agent 144 may communicate with a secondary storage device 108 via a suitable communications link, such as a SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database 152. Media agent database 152 may be stored to a disk or other storage device (not shown) that is local to the secondary storage computing device 106 on which media agent 144 executes. In other cases, media agent database 152 is stored separately from the host secondary storage computing device 106. Media agent database 152 can include, among other things, a media agent index 153 (see, e.g., FIG. 1C). In some cases, media agent index 153 does not form a part of and is instead separate from media agent database 152.

Media agent index 153 (or “index 153”) may be a data structure associated with the particular media agent 144 that includes information about the stored data associated with the particular media agent and which may be generated in the course of performing a secondary copy operation or a restore. Index 153 provides a fast and efficient mechanism for locating/browsing secondary copies 116 or other data stored in secondary storage devices 108 without having to access secondary storage device 108 to retrieve the information from there. For instance, for each secondary copy 116, index 153 may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a logical path to the secondary copy 116 on the corresponding secondary storage device 108, location information (e.g., offsets) indicating where the data objects are stored in the secondary storage device 108, when the data objects were created or modified, etc. Thus, index 153 includes metadata associated with the secondary copies 116 that is readily available for use from media agent 144. In some embodiments, some or all of the information in index 153 may instead or additionally be stored along with secondary copies 116 in secondary storage device 108. In some embodiments, a secondary storage device 108 can include sufficient information to enable a “bare metal restore,” where the operating system and/or software applications of a failed client computing device 102 or another target may be automatically restored without manually reinstalling individual software packages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to as an “index cache.” In such cases, information stored in index cache 153 typically comprises data that reflects certain particulars about relatively recent secondary copy operations. After some triggering event, such as after some time elapses or index cache 153 reaches a particular size, certain portions of index cache 153 may be copied or migrated to secondary storage device 108, e.g., on a least-recently-used basis. This information may be retrieved and uploaded back into index cache 153 or otherwise restored to media agent 144 to facilitate retrieval of data from the secondary storage device(s) 108. In some embodiments, the cached information may include format or containerization information related to archives or other files stored on storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as a coordinator or facilitator of secondary copy operations between client computing devices 102 and secondary storage devices 108, but does not actually write the data to secondary storage device 108. For instance, storage manager 140 (or media agent 144) may instruct a client computing device 102 and secondary storage device 108 to communicate with one another directly. In such a case, client computing device 102 transmits data directly or via one or more intermediary components to secondary storage device 108 according to the received instructions, and vice versa. Media agent 144 may still receive, process, and/or maintain metadata related to the secondary copy operations, i.e., may continue to build and maintain index 153. In these embodiments, payload data can flow through media agent 144 for the purposes of populating index 153, but not for writing to secondary storage device 108. Media agent 144 and/or other components such as storage manager 140 may in some cases incorporate additional functionality, such as data classification, content indexing, deduplication, encryption, compression, and the like. Further details regarding these and other functions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongst various physical and/or logical components. For instance, one or more of storage manager 140, data agents 142, and media agents 144 may operate on computing devices that are physically separate from one another. This architecture can provide a number of benefits. For instance, hardware and software design choices for each distributed component can be targeted to suit its particular function. The secondary computing devices 106 on which media agents 144 operate can be tailored for interaction with associated secondary storage devices 108 and provide fast index cache operation, among other specific tasks. Similarly, client computing device(s) 102 can be selected to effectively service applications 110 in order to efficiently produce and store primary data 112.

Moreover, in some cases, one or more of the individual components of information management system 100 can be distributed to multiple separate computing devices. As one example, for large file systems where the amount of data stored in management database 146 is relatively large, database 146 may be migrated to or may otherwise reside on a specialized database server (e.g., an SQL server) separate from a server that implements the other functions of storage manager 140. This distributed configuration can provide added protection because database 146 can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of storage manager 140. Database 146 can be efficiently replicated to a remote site for use in the event of a disaster or other data loss at the primary site. Or database 146 can be replicated to another computing device within the same site, such as to a higher performance machine in the event that a storage manager host computing device can no longer service the needs of a growing system 100.

The distributed architecture also provides scalability and efficient component utilization. FIG. 1D shows an embodiment of information management system 100 including a plurality of client computing devices 102 and associated data agents 142 as well as a plurality of secondary storage computing devices 106 and associated media agents 144. Additional components can be added or subtracted based on the evolving needs of system 100. For instance, depending on where bottlenecks are identified, administrators can add additional client computing devices 102, secondary storage computing devices 106, and/or secondary storage devices 108. Moreover, where multiple fungible components are available, load balancing can be implemented to dynamically address identified bottlenecks. As an example, storage manager 140 may dynamically select which media agents 144 and/or secondary storage devices 108 to use for storage operations based on a processing load analysis of media agents 144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG. 1D), a first media agent 144 may provide failover functionality for a second failed media agent 144. In addition, media agents 144 can be dynamically selected to provide load balancing. Each client computing device 102 can communicate with, among other components, any of the media agents 144, e.g., as directed by storage manager 140. And each media agent 144 may communicate with, among other components, any of secondary storage devices 108, e.g., as directed by storage manager 140. Thus, operations can be routed to secondary storage devices 108 in a dynamic and highly flexible manner, to provide load balancing, failover, etc. Further examples of scalable systems capable of dynamic storage operations, load balancing, and failover are provided in U.S. Pat. No. 7,246,207.

While distributing functionality amongst multiple computing devices can have certain advantages, in other contexts it can be beneficial to consolidate functionality on the same computing device. In alternative configurations, certain components may reside and execute on the same computing device. As such, in other embodiments, one or more of the components shown in FIG. 1C may be implemented on the same computing device. In one configuration, a storage manager 140, one or more data agents 142, and/or one or more media agents 144 are all implemented on the same computing device. In other embodiments, one or more data agents 142 and one or more media agents 144 are implemented on the same computing device, while storage manager 140 is implemented on a separate computing device, etc. without limitation.

Example Types of Information Management Operations, Including Storage Operations

In order to protect and leverage stored data, system 100 can be configured to perform a variety of information management operations, which may also be referred to in some cases as storage management operations or storage operations. These operations can generally include (i) data movement operations, (ii) processing and data manipulation operations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involve the copying or migration of data between different locations in system 100. For example, data movement operations can include operations in which stored data is copied, migrated, or otherwise transferred from one or more first storage devices to one or more second storage devices, such as from primary storage device(s) 104 to secondary storage device(s) 108, from secondary storage device(s) 108 to different secondary storage device(s) 108, from secondary storage devices 108 to primary storage devices 104, or from primary storage device(s) 104 to different primary storage device(s) 104, or in some cases within the same primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backup operations, archive operations, information lifecycle management operations such as hierarchical storage management operations, replication operations (e.g., continuous data replication), snapshot operations, deduplication or single-instancing operations, auxiliary copy operations, disaster-recovery copy operations, and the like. As will be discussed, some of these operations do not necessarily create distinct copies. Nonetheless, some or all of these operations are generally referred to as “secondary copy operations” for simplicity because they involve secondary copies. Data movement also comprises restoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at a particular point in time (e.g., one or more files or other data units). Each subsequent backup copy 116 (which is a form of secondary copy 116) may be maintained independently of the first. A backup generally involves maintaining a version of the copied primary data 112 as well as backup copies 116. Further, a backup copy in some embodiments is generally stored in a form that is different from the native format, e.g., a backup format. This contrasts to the version in primary data 112 which may instead be stored in a format native to the source application(s) 110. In various cases, backup copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original native application format. For example, a backup copy may be stored in a compressed backup format that facilitates efficient long-term storage. Backup copies 116 can have relatively long retention periods as compared to primary data 112, which is generally highly changeable. Backup copies 116 may be stored on media with slower retrieval times than primary storage device 104. Some backup copies may have shorter retention periods than some other types of secondary copies 116, such as archive copies (described below). Backups may be stored at an offsite location.

Backup operations can include full backups, differential backups, incremental backups, “synthetic full” backups, and/or creating a “reference copy.” A full backup (or “standard full backup”) in some embodiments is generally a complete image of the data to be protected. However, because full backup copies can consume a relatively large amount of storage, it can be useful to use a full backup copy as a baseline and only store changes relative to the full backup copy afterwards.

A differential backup operation (or cumulative incremental backup operation) tracks and stores changes that occurred since the last full backup. Differential backups can grow quickly in size, but can restore relatively efficiently because a restore can be completed in some cases using only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changes since the most recent backup copy of any type, which can greatly reduce storage utilization. In some cases, however, restoring can be lengthy compared to full or differential backups because completing a restore operation may involve accessing a full backup in addition to multiple incremental backups.

Synthetic full backups generally consolidate data without directly backing up data from the client computing device. A synthetic full backup is created from the most recent full backup (i.e., standard or synthetic) and subsequent incremental and/or differential backups. The resulting synthetic full backup is identical to what would have been created had the last backup for the subclient been a standard full backup. Unlike standard full, incremental, and differential backups, however, a synthetic full backup does not actually transfer data from primary storage to the backup media, because it operates as a backup consolidator. A synthetic full backup extracts the index data of each participating subclient. Using this index data and the previously backed up user data images, it builds new full backup images (e.g., bitmaps), one for each subclient. The new backup images consolidate the index and user data stored in the related incremental, differential, and previous full backups into a synthetic backup file that fully represents the subclient (e.g., via pointers) but does not comprise all its constituent data.

Any of the above types of backup operations can be at the volume level, file level, or block level. Volume level backup operations generally involve copying of a data volume (e.g., a logical disk or partition) as a whole. In a file-level backup, information management system 100 generally tracks changes to individual files and includes copies of files in the backup copy. For block-level backups, files are broken into constituent blocks, and changes are tracked at the block level. Upon restore, system 100 reassembles the blocks into files in a transparent fashion. Far less data may actually be transferred and copied to secondary storage devices 108 during a file-level copy than a volume-level copy. Likewise, a block-level copy may transfer less data than a file-level copy, resulting in faster execution. However, restoring a relatively higher-granularity copy can result in longer restore times. For instance, when restoring a block-level copy, the process of locating and retrieving constituent blocks can sometimes take longer than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backed up data, typically to help organize data by keeping contextual information from multiple sources together, and/or help retain specific data for a longer period of time, such as for legal hold needs. A reference copy generally maintains data integrity, and when the data is restored, it may be viewed in the same format as the source data. In some embodiments, a reference copy is based on a specialized client, individual subclient and associated information management policies (e.g., storage policy, retention policy, etc.) that are administered within system 100.

Archive Operations

Because backup operations generally involve maintaining a version of the copied primary data 112 and also maintaining backup copies in secondary storage device(s) 108, they can consume significant storage capacity. To reduce storage consumption, an archive operation according to certain embodiments creates an archive copy 116 by both copying and removing source data. Or, seen another way, archive operations can involve moving some or all of the source data to the archive destination. Thus, data satisfying criteria for removal (e.g., data of a threshold age or size) may be removed from source storage. The source data may be primary data 112 or a secondary copy 116, depending on the situation. As with backup copies, archive copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the format of the original application or source copy. In addition, archive copies may be retained for relatively long periods of time (e.g., years) and, in some cases are never deleted. In certain embodiments, archive copies may be made and kept for extended periods in order to meet compliance regulations.

Archiving can also serve the purpose of freeing up space in primary storage device(s) 104 and easing the demand on computational resources on client computing device 102. Similarly, when a secondary copy 116 is archived, the archive copy can therefore serve the purpose of freeing up space in the source secondary storage device(s) 108. Examples of data archiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficient mechanism for protecting data. From an end-user viewpoint, a snapshot may be thought of as an “instant” image of primary data 112 at a given point in time, and may include state and/or status information relative to an application 110 that creates/manages primary data 112. In one embodiment, a snapshot may generally capture the directory structure of an object in primary data 112 such as a file or volume or other data set at a particular moment in time and may also preserve file attributes and contents. A snapshot in some cases is created relatively quickly, e.g., substantially instantly, using a minimum amount of file space, but may still function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurs where a target storage device (e.g., a primary storage device 104 or a secondary storage device 108) performs the snapshot operation in a self-contained fashion, substantially independently, using hardware, firmware and/or software operating on the storage device itself. For instance, the storage device may perform snapshot operations generally without intervention or oversight from any of the other components of the system 100, e.g., a storage array may generate an “array-created” hardware snapshot and may also manage its storage, integrity, versioning, etc. In this manner, hardware snapshots can off-load other components of system 100 from snapshot processing. An array may receive a request from another component to take a snapshot and then proceed to execute the “hardware snapshot” operations autonomously, preferably reporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on the other hand, occurs where a component in system 100 (e.g., client computing device 102, etc.) implements a software layer that manages the snapshot operation via interaction with the target storage device. For instance, the component executing the snapshot management software layer may derive a set of pointers and/or data that represents the snapshot. The snapshot management software layer may then transmit the same to the target storage device, along with appropriate instructions for writing the snapshot. One example of a software snapshot product is Microsoft Volume Snapshot Service (VSS), which is part of the Microsoft Windows operating system.

Some types of snapshots do not actually create another physical copy of all the data as it existed at the particular point in time, but may simply create pointers that map files and directories to specific memory locations (e.g., to specific disk blocks) where the data resides as it existed at the particular point in time. For example, a snapshot copy may include a set of pointers derived from the file system or from an application. In some other cases, the snapshot may be created at the block-level, such that creation of the snapshot occurs without awareness of the file system. Each pointer points to a respective stored data block, so that collectively, the set of pointers reflect the storage location and state of the data object (e.g., file(s) or volume(s) or data set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the file system. Additional disk space is usually required only when files and directories change later on. Furthermore, when files change, typically only the pointers which map to blocks are copied, not the blocks themselves. For example for “copy-on-write” snapshots, when a block changes in primary storage, the block is copied to secondary storage or cached in primary storage before the block is overwritten in primary storage, and the pointer to that block is changed to reflect the new location of that block. The snapshot mapping of file system data may also be updated to reflect the changed block(s) at that particular point in time. In some other cases, a snapshot includes a full physical copy of all or substantially all of the data represented by the snapshot. Further examples of snapshot operations are provided in U.S. Pat. No. 7,529,782. A snapshot copy in many cases can be made quickly and without significantly impacting primary computing resources because large amounts of data need not be copied or moved. In some embodiments, a snapshot may exist as a virtual file system, parallel to the actual file system. Users in some cases gain read-only access to the record of files and directories of the snapshot. By electing to restore primary data 112 from a snapshot taken at a given point in time, users may also return the current file system to the state of the file system that existed when the snapshot was taken.

Replication Operations

Replication is another type of secondary copy operation. Some types of secondary copies 116 periodically capture images of primary data 112 at particular points in time (e.g., backups, archives, and snapshots). However, it can also be useful for recovery purposes to protect primary data 112 in a more continuous fashion, by replicating primary data 112 substantially as changes occur. In some cases a replication copy can be a mirror copy, for instance, where changes made to primary data 112 are mirrored or substantially immediately copied to another location (e.g., to secondary storage device(s) 108). By copying each write operation to the replication copy, two storage systems are kept synchronized or substantially synchronized so that they are virtually identical at approximately the same time. Where entire disk volumes are mirrored, however, mirroring can require significant amount of storage space and utilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performed on replicated data that represents a recoverable state, or “known good state” of a particular application running on the source system. For instance, in certain embodiments, known good replication copies may be viewed as copies of primary data 112. This feature allows the system to directly access, copy, restore, back up, or otherwise manipulate the replication copies as if they were the “live” primary data 112. This can reduce access time, storage utilization, and impact on source applications 110, among other benefits. Based on known good state information, system 100 can replicate sections of application data that represent a recoverable state rather than rote copying of blocks of data. Examples of replication operations (e.g., continuous data replication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amount of non-primary data. For instance, some or all of the above-described secondary copy operations can involve deduplication in some fashion. New data is read, broken down into data portions of a selected granularity (e.g., sub-file level blocks, files, etc.), compared with corresponding portions that are already in secondary storage, and only new/changed portions are stored. Portions that already exist are represented as pointers to the already-stored data. Thus, a deduplicated secondary copy 116 may comprise actual data portions copied from or based on primary data 112 and may further comprise pointers to already-stored data, which is generally more storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculate and/or store signatures (e.g., hashes or cryptographically unique IDs) corresponding to the individual source data portions extracted from primary data 112 and compare the signatures to already-stored data signatures, instead of comparing entire data portions. The signatures of already-stored data are maintained in a deduplication database. In some cases, only a single instance of each data portion is stored, and deduplication operations may therefore be referred to interchangeably as “single-instancing” operations. Depending on the implementation, however, deduplication operations can store more than one instance of certain data portions, yet still significantly reduce stored-data redundancy. Depending on the embodiment, deduplication portions such as data blocks can be of fixed or variable length. Using variable length blocks can enhance deduplication by responding to changes in the data stream, but can involve more complex processing. In some cases, system 100 utilizes a technique for dynamically aligning deduplication blocks based on changing content in the data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety of locations. For instance, in some embodiments, system 100 implements “target-side” deduplication by deduplicating data at the media agent 144 after being received from data agent 142. In some such cases, media agents 144 are generally configured to manage the deduplication process. For instance, one or more of the media agents 144 maintain a corresponding deduplication database that stores deduplication information (e.g., data block signatures). Examples of such a configuration are provided in U.S. Pat. No. 9,020,900. Instead of or in combination with “target-side” deduplication, “source-side” (or “client-side”) deduplication can also be performed, e.g., to reduce the amount of data to be transmitted by data agent 142 to media agent 144. In client-side deduplication, data agent 142 is responsible for checking signatures before preparing a data stream for media agent 144, and if a signature finds a match in the deduplication database, data agent 142 transmits a pointer rather than the payload data to media agent 144. Storage manager 140 may communicate with other components within system 100 via network protocols and cloud service provider APIs to facilitate cloud-based deduplication/single instancing, as exemplified in U.S. Pat. No. 8,954,446. Some other deduplication/single instancing techniques are described in U.S. Patent Pub. No. 2006/0224846 and in U.S. Pat. No. 9,098,495. See also FIG. 1H.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move from more expensive quick-access storage to less expensive slower-access storage. Operations associated with moving data through various tiers of storage are sometimes referred to as information lifecycle management (ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM) operation, which generally automatically moves data between classes of storage devices, such as from high-cost to low-cost storage devices. For instance, an HSM operation may involve movement of data from primary storage devices 104 to secondary storage devices 108, or between tiers of secondary storage devices 108. With each tier, the storage devices may be progressively cheaper, have relatively slower access/restore times, etc. For example, movement of data between tiers may occur as data becomes less important over time. In some embodiments, an HSM operation is similar to archiving in that creating an HSM copy may (though not always) involve deleting some of the source data, e.g., according to one or more criteria related to the source data. For example, an HSM copy may include primary data 112 or a secondary copy 116 that exceeds a given size threshold or a given age threshold. Often, and unlike some types of archive copies, HSM data that is removed or aged from the source is replaced by a logical reference pointer or stub. The reference pointer or stub can be stored in the primary storage device 104 or other source storage device, such as a secondary storage device 108 to replace the deleted source data and to point to or otherwise indicate the new location in (another) secondary storage device 108.

For example, files are generally moved between higher and lower cost storage depending on how often the files are accessed. When a user requests access to HSM data that has been removed or migrated, system 100 uses the stub to locate the data and can make recovery of the data appear transparent, even though the HSM data may be stored at a location different from other source data. In this manner, the data appears to the user (e.g., in file system browsing windows and the like) as if it still resides in the source location (e.g., in a primary storage device 104). The stub may include metadata associated with the corresponding data, so that a file system and/or application can provide some information about the data object and/or a limited-functionality version (e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native application format (e.g., compressed, encrypted, deduplicated, and/or otherwise modified). In some cases, copies which involve the removal of data from source storage and the maintenance of stub or other logical reference information on source storage may be referred to generally as “on-line archive copies.” On the other hand, copies which involve the removal of data from source storage without the maintenance of stub or other logical reference information on source storage may be referred to as “off-line archive copies.” Examples of HSM and ILM techniques are provided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116. For instance, an initial secondary copy 116 may be derived from primary data 112 or from data residing in secondary storage subsystem 118, whereas an auxiliary copy is generated from the initial secondary copy 116. Auxiliary copies provide additional standby copies of data and may reside on different secondary storage devices 108 than the initial secondary copies 116. Thus, auxiliary copies can be used for recovery purposes if initial secondary copies 116 become unavailable. Example auxiliary copy techniques are described in further detail in U.S. Pat. No. 8,230,195.

Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often as secondary, high-availability disk copies. System 100 may create secondary copies and store them at disaster recovery locations using auxiliary copy or replication operations, such as continuous data replication technologies. Depending on the particular data protection goals, disaster recovery locations can be remote from the client computing devices 102 and primary storage devices 104, remote from some or all of the secondary storage devices 108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compression as well as integrity marking and checking, formatting for transmission, formatting for storage, etc. Data may be manipulated “client-side” by data agent 142 as well as “target-side” by media agent 144 in the course of creating secondary copy 116, or conversely in the course of restoring data from secondary to primary.

Encryption Operations

System 100 in some cases is configured to process data (e.g., files or other data objects, primary data 112, secondary copies 116, etc.), according to an appropriate encryption algorithm (e.g., Blowfish, Advanced Encryption Standard (AES), Triple Data Encryption Standard (3-DES), etc.) to limit access and provide data security. System 100 in some cases encrypts the data at the client level, such that client computing devices 102 (e.g., data agents 142) encrypt the data prior to transferring it to other components, e.g., before sending the data to media agents 144 during a secondary copy operation. In such cases, client computing device 102 may maintain or have access to an encryption key or passphrase for decrypting the data upon restore. Encryption can also occur when media agent 144 creates auxiliary copies or archive copies. Encryption may be applied in creating a secondary copy 116 of a previously unencrypted secondary copy 116, without limitation. In further embodiments, secondary storage devices 108 can implement built-in, high performance hardware-based encryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compress data in the course of generating a secondary copy 116. Compression encodes information such that fewer bits are needed to represent the information as compared to the original representation. Compression techniques are well known in the art. Compression operations may apply one or more data compression algorithms. Compression may be applied in creating a secondary copy 116 of a previously uncompressed secondary copy, e.g., when making archive copies or disaster recovery copies. The use of compression may result in metadata that specifies the nature of the compression, so that data may be uncompressed on restore if appropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from data movement operations in that they do not necessarily involve copying, migration or other transfer of data between different locations in the system. For instance, data analysis operations may involve processing (e.g., offline processing) or modification of already stored primary data 112 and/or secondary copies 116. However, in some embodiments data analysis operations are performed in conjunction with data movement operations. Some data analysis operations include content indexing operations and classification operations which can be useful in leveraging data under management to enhance search and other features.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes and indexes characteristics, content, and metadata associated with primary data 112 (“online content indexing”) and/or secondary copies 116 (“off-line content indexing”). Content indexing can identify files or other data objects based on content (e.g., user-defined keywords or phrases, other keywords/phrases that are not defined by a user, etc.), and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,” attachment name, received time, etc.). Content indexes may be searched and search results may be restored.

System 100 generally organizes and catalogues the results into a content index, which may be stored within media agent database 152, for example. The content index can also include the storage locations of or pointer references to indexed data in primary data 112 and/or secondary copies 116. Results may also be stored elsewhere in system 100 (e.g., in primary storage device 104 or in secondary storage device 108). Such content index data provides storage manager 140 or other components with an efficient mechanism for locating primary data 112 and/or secondary copies 116 of data objects that match particular criteria, thus greatly increasing the search speed capability of system 100. For instance, search criteria can be specified by a user through user interface 158 of storage manager 140. Moreover, when system 100 analyzes data and/or metadata in secondary copies 116 to create an “off-line content index,” this operation has no significant impact on the performance of client computing devices 102 and thus does not take a toll on the production environment. Examples of content indexing techniques are provided in U.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can be configured to scan data and/or associated metadata for classification purposes to populate a database (or other data structure) of information, which can be referred to as a “data classification database” or a “metabase.” Depending on the embodiment, the data classification database(s) can be organized in a variety of different ways, including centralization, logical sub-divisions, and/or physical sub-divisions. For instance, one or more data classification databases may be associated with different subsystems or tiers within system 100. As an example, there may be a first metabase associated with primary storage subsystem 117 and a second metabase associated with secondary storage subsystem 118. In other cases, metabase(s) may be associated with individual components, e.g., client computing devices 102 and/or media agents 144. In some embodiments, a data classification database may reside as one or more data structures within management database 146, may be otherwise associated with storage manager 140, and/or may reside as a separate component. In some cases, metabase(s) may be included in separate database(s) and/or on separate storage device(s) from primary data 112 and/or secondary copies 116, such that operations related to the metabase(s) do not significantly impact performance on other components of system 100. In other cases, metabase(s) may be stored along with primary data 112 and/or secondary copies 116. Files or other data objects can be associated with identifiers (e.g., tag entries, etc.) to facilitate searches of stored data objects. Among a number of other benefits, the metabase can also allow efficient, automatic identification of files or other data objects to associate with secondary copy or other information management operations. For instance, a metabase can dramatically improve the speed with which system 100 can search through and identify data as compared to other approaches that involve scanning an entire file system. Examples of metabases and data classification operations are provided in U.S. Pat. Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system 100 to provide useful system-wide management and reporting. Operations management can generally include monitoring and managing the health and performance of system 100 by, without limitation, performing error tracking, generating granular storage/performance metrics (e.g., job success/failure information, deduplication efficiency, etc.), generating storage modeling and costing information, and the like. As an example, storage manager 140 or another component in system 100 may analyze traffic patterns and suggest and/or automatically route data to minimize congestion. In some embodiments, the system can generate predictions relating to storage operations or storage operation information. Such predictions, which may be based on a trending analysis, may predict various network operations or resource usage, such as network traffic levels, storage media use, use of bandwidth of communication links, use of media agent components, etc. Further examples of traffic analysis, trend analysis, prediction generation, and the like are described in U.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, a master storage manager 140 may track the status of subordinate cells, such as the status of jobs, system components, system resources, and other items, by communicating with storage managers 140 (or other components) in the respective storage operation cells. Moreover, the master storage manager 140 may also track status by receiving periodic status updates from the storage managers 140 (or other components) in the respective cells regarding jobs, system components, system resources, and other items. In some embodiments, a master storage manager 140 may store status information and other information regarding its associated storage operation cells and other system information in its management database 146 and/or index 150 (or in another location). The master storage manager 140 or other component may also determine whether certain storage-related or other criteria are satisfied, and may perform an action or trigger event (e.g., data migration) in response to the criteria being satisfied, such as where a storage threshold is met for a particular volume, or where inadequate protection exists for certain data. For instance, data from one or more storage operation cells is used to mitigate recognized risks dynamically and automatically, and/or to advise users of risks or suggest actions to mitigate these risks. For example, an information management policy may specify certain requirements (e.g., that a storage device should maintain a certain amount of free space, that secondary copies should occur at a particular interval, that data should be aged and migrated to other storage after a particular period, that data on a secondary volume should always have a certain level of availability and be restorable within a given time period, that data on a secondary volume may be mirrored or otherwise migrated to a specified number of other volumes, etc.). If a risk condition or other criterion is triggered, the system may notify the user of these conditions and may suggest (or automatically implement) a mitigation action to address the risk. For example, the system may indicate that data from a primary copy 112 should be migrated to a secondary storage device 108 to free up space on primary storage device 104. Examples of the use of risk factors and other triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric or other indication satisfies particular storage criteria sufficient to perform an action. For example, a storage policy or other definition might indicate that a storage manager 140 should initiate a particular action if a storage metric or other indication drops below or otherwise fails to satisfy specified criteria such as a threshold of data protection. In some embodiments, risk factors may be quantified into certain measurable service or risk levels. For example, certain applications and associated data may be considered to be more important relative to other data and services. Financial compliance data, for example, may be of greater importance than marketing materials, etc. Network administrators may assign priority values or “weights” to certain data and/or applications corresponding to the relative importance. The level of compliance of secondary copy operations specified for these applications may also be assigned a certain value. Thus, the health, impact, and overall importance of a service may be determined, such as by measuring the compliance value and calculating the product of the priority value and the compliance value to determine the “service level” and comparing it to certain operational thresholds to determine whether it is acceptable. Further examples of the service level determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availability associated with information management operation cells. For instance, data received from a cell may be used in conjunction with hardware-related information and other information about system elements to determine the cost of storage and/or the availability of particular data. Example information generated could include how fast a particular department is using up available storage space, how long data would take to recover over a particular pathway from a particular secondary storage device, costs over time, etc. Moreover, in some embodiments, such information may be used to determine or predict the overall cost associated with the storage of certain information. The cost associated with hosting a certain application may be based, at least in part, on the type of media on which the data resides, for example. Storage devices may be assigned to a particular cost categories, for example. Further examples of costing techniques are described in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related to trending, predictions, job, cell or component status, risk, service level, costing, etc.) can generally be provided to users via user interface 158 in a single integrated view or console (not shown). Report types may include: scheduling, event management, media management and data aging. Available reports may also include backup history, data aging history, auxiliary copy history, job history, library and drive, media in library, restore history, and storage policy, etc., without limitation. Such reports may be specified and created at a certain point in time as a system analysis, forecasting, or provisioning tool. Integrated reports may also be generated that illustrate storage and performance metrics, risks and storage costing information. Moreover, users may create their own reports based on specific needs. User interface 158 can include an option to graphically depict the various components in the system using appropriate icons. As one example, user interface 158 may provide a graphical depiction of primary storage devices 104, secondary storage devices 108, data agents 142 and/or media agents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 can facilitate planning and decision-making. For example, in some embodiments, a user may view the status of some or all jobs as well as the status of each component of information management system 100. Users may then plan and make decisions based on this data. For instance, a user may view high-level information regarding secondary copy operations for system 100, such as job status, component status, resource status (e.g., communication pathways, etc.), and other information. The user may also drill down or use other means to obtain more detailed information regarding a particular component, job, or the like. Further examples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discovery operations in some embodiments. In general, e-discovery operations provide a unified collection and search capability for data in the system, such as data stored in secondary storage devices 108 (e.g., backups, archives, or other secondary copies 116). For example, system 100 may construct and maintain a virtual repository for data stored in system 100 that is integrated across source applications 110, different storage device types, etc. According to some embodiments, e-discovery utilizes other techniques described herein, such as data classification and/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with secondary copy and/or other information management operations.

One type of information management policy 148 is a “storage policy.” According to certain embodiments, a storage policy generally comprises a data structure or other information source that defines (or includes information sufficient to determine) a set of preferences or other criteria for performing information management operations. Storage policies can include one or more of the following: (1) what data will be associated with the storage policy, e.g., subclient; (2) a destination to which the data will be stored; (3) datapath information specifying how the data will be communicated to the destination; (4) the type of secondary copy operation to be performed; and (5) retention information specifying how long the data will be retained at the destination (see, e.g., FIG. 1E). Data associated with a storage policy can be logically organized into subclients, which may represent primary data 112 and/or secondary copies 116. A subclient may represent static or dynamic associations of portions of a data volume. Subclients may represent mutually exclusive portions. Thus, in certain embodiments, a portion of data may be given a label and the association is stored as a static entity in an index, database or other storage location. Subclients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, or the like. Depending on the configuration, subclients can correspond to files, folders, virtual machines, databases, etc. In one example scenario, an administrator may find it preferable to separate e-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a target or destination storage device (or group of storage devices). For instance, where the secondary storage device 108 includes a group of disk libraries, the storage policy may specify a particular disk library for storing the subclients associated with the policy. As another example, where the secondary storage devices 108 include one or more tape libraries, the storage policy may specify a particular tape library for storing the subclients associated with the storage policy, and may also specify a drive pool and a tape pool defining a group of tape drives and a group of tapes, respectively, for use in storing the subclient data. While information in the storage policy can be statically assigned in some cases, some or all of the information in the storage policy can also be dynamically determined based on criteria set forth in the storage policy. For instance, based on such criteria, a particular destination storage device(s) or other parameter of the storage policy may be determined based on characteristics associated with the data involved in a particular secondary copy operation, device availability (e.g., availability of a secondary storage device 108 or a media agent 144), network status and conditions (e.g., identified bottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. For instance, the storage policy may specify network pathways and components to utilize when moving the data to the destination storage device(s). In some embodiments, the storage policy specifies one or more media agents 144 for conveying data associated with the storage policy between the source and destination. A storage policy can also specify the type(s) of associated operations, such as backup, archive, snapshot, auxiliary copy, or the like. Furthermore, retention parameters can specify how long the resulting secondary copies 116 will be kept (e.g., a number of days, months, years, etc.), perhaps depending on organizational needs and/or compliance criteria.

When adding a new client computing device 102, administrators can manually configure information management policies 148 and/or other settings, e.g., via user interface 158. However, this can be an involved process resulting in delays, and it may be desirable to begin data protection operations quickly, without awaiting human intervention. Thus, in some embodiments, system 100 automatically applies a default configuration to client computing device 102. As one example, when one or more data agent(s) 142 are installed on a client computing device 102, the installation script may register the client computing device 102 with storage manager 140, which in turn applies the default configuration to the new client computing device 102. In this manner, data protection operations can begin substantially immediately. The default configuration can include a default storage policy, for example, and can specify any appropriate information sufficient to begin data protection operations. This can include a type of data protection operation, scheduling information, a target secondary storage device 108, data path information (e.g., a particular media agent 144), and the like.

Another type of information management policy 148 is a “scheduling policy,” which specifies when and how often to perform operations. Scheduling parameters may specify with what frequency (e.g., hourly, weekly, daily, event-based, etc.) or under what triggering conditions secondary copy or other information management operations are to take place. Scheduling policies in some cases are associated with particular components, such as a subclient, client computing device 102, and the like.

Another type of information management policy 148 is an “audit policy” (or “security policy”), which comprises preferences, rules and/or criteria that protect sensitive data in system 100. For example, an audit policy may define “sensitive objects” which are files or data objects that contain particular keywords (e.g., “confidential,” or “privileged”) and/or are associated with particular keywords (e.g., in metadata) or particular flags (e.g., in metadata identifying a document or email as personal, confidential, etc.). An audit policy may further specify rules for handling sensitive objects. As an example, an audit policy may require that a reviewer approve the transfer of any sensitive objects to a cloud storage site, and that if approval is denied for a particular sensitive object, the sensitive object should be transferred to a local primary storage device 104 instead. To facilitate this approval, the audit policy may further specify how a secondary storage computing device 106 or other system component should notify a reviewer that a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioning policy,” which can include preferences, priorities, rules, and/or criteria that specify how client computing devices 102 (or groups thereof) may utilize system resources, such as available storage on cloud storage and/or network bandwidth. A provisioning policy specifies, for example, data quotas for particular client computing devices 102 (e.g., a number of gigabytes that can be stored monthly, quarterly or annually). Storage manager 140 or other components may enforce the provisioning policy. For instance, media agents 144 may enforce the policy when transferring data to secondary storage devices 108. If a client computing device 102 exceeds a quota, a budget for the client computing device 102 (or associated department) may be adjusted accordingly or an alert may trigger.

While the above types of information management policies 148 are described as separate policies, one or more of these can be generally combined into a single information management policy 148. For instance, a storage policy may also include or otherwise be associated with one or more scheduling, audit, or provisioning policies or operational parameters thereof. Moreover, while storage policies are typically associated with moving and storing data, other policies may be associated with other types of information management operations. The following is a non-exhaustive list of items that information management policies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when         and/or how often to perform information management operations;     -   the type of secondary copy 116 and/or copy format (e.g.,         snapshot, backup, archive, HSM, etc.);     -   a location or a class or quality of storage for storing         secondary copies 116 (e.g., one or more particular secondary         storage devices 108);     -   preferences regarding whether and how to encrypt, compress,         deduplicate, or otherwise modify or transform secondary copies         116;     -   which system components and/or network pathways (e.g., preferred         media agents 144) should be used to perform secondary storage         operations;     -   resource allocation among different computing devices or other         system components used in performing information management         operations (e.g., bandwidth allocation, available storage         capacity, etc.);     -   whether and how to synchronize or otherwise distribute files or         other data objects across multiple computing devices or hosted         services; and retention information specifying the length of         time primary data 112 and/or secondary copies 116 should be         retained, e.g., in a particular class or tier of storage         devices, or within the system 100.

Information management policies 148 can additionally specify or depend on historical or current criteria that may be used to determine which rules to apply to a particular data object, system component, or information management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of         a data object or metadata has been or is predicted to be used,         accessed, or modified;     -   time-related factors (e.g., aging information such as time since         the creation or modification of a data object);     -   deduplication information (e.g., hashes, data blocks,         deduplication block size, deduplication efficiency or other         metrics);     -   an estimated or historic usage or cost associated with different         components (e.g., with secondary storage devices 108);     -   the identity of users, applications 110, client computing         devices 102 and/or other computing devices that created,         accessed, modified, or otherwise utilized primary data 112 or         secondary copies 116;     -   a relative sensitivity (e.g., confidentiality, importance) of a         data object, e.g., as determined by its content and/or metadata;     -   the current or historical storage capacity of various storage         devices;     -   the current or historical network capacity of network pathways         connecting various components within the storage operation cell;     -   access control lists or other security information; and     -   the content of a particular data object (e.g., its textual         content) or of metadata associated with the data object.

Example Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondary copy operations by an embodiment of information management system 100, according to an example storage policy 148A. System 100 includes a storage manager 140, a client computing device 102 having a file system data agent 142A and an email data agent 142B operating thereon, a primary storage device 104, two media agents 144A, 144B, and two secondary storage devices 108: a disk library 108A and a tape library 108B. As shown, primary storage device 104 includes primary data 112A, which is associated with a logical grouping of data associated with a file system (“file system subclient”), and primary data 112B, which is a logical grouping of data associated with email (“email subclient”). The techniques described with respect to FIG. 1E can be utilized in conjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tape library 108B are “off-site,” and may be remotely located from the other components in system 100 (e.g., in a different city, office building, etc.). Indeed, “off-site” may refer to a magnetic tape located in remote storage, which must be manually retrieved and loaded into a tape drive to be read. In this manner, information stored on the tape library 108B may provide protection in the event of a disaster or other failure at the main site(s) where data is stored.

The file system subclient 112A in certain embodiments generally comprises information generated by the file system and/or operating system of client computing device 102, and can include, for example, file system data (e.g., regular files, file tables, mount points, etc.), operating system data (e.g., registries, event logs, etc.), and the like. The e-mail subclient 112B can include data generated by an e-mail application operating on client computing device 102, e.g., mailbox information, folder information, emails, attachments, associated database information, and the like. As described above, the subclients can be logical containers, and the data included in the corresponding primary data 112A and 112B may or may not be stored contiguously.

The example storage policy 148A includes backup copy preferences or rule set 160, disaster recovery copy preferences or rule set 162, and compliance copy preferences or rule set 164. Backup copy rule set 160 specifies that it is associated with file system subclient 166 and email subclient 168. Each of subclients 166 and 168 are associated with the particular client computing device 102. Backup copy rule set 160 further specifies that the backup operation will be written to disk library 108A and designates a particular media agent 144A to convey the data to disk library 108A. Finally, backup copy rule set 160 specifies that backup copies created according to rule set 160 are scheduled to be generated hourly and are to be retained for 30 days. In some other embodiments, scheduling information is not included in storage policy 148A and is instead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same two subclients 166 and 168. However, disaster recovery copy rule set 162 is associated with tape library 108B, unlike backup copy rule set 160. Moreover, disaster recovery copy rule set 162 specifies that a different media agent, namely 144B, will convey data to tape library 108B. Disaster recovery copies created according to rule set 162 will be retained for 60 days and will be generated daily. Disaster recovery copies generated according to disaster recovery copy rule set 162 can provide protection in the event of a disaster or other catastrophic data loss that would affect the backup copy 116A maintained on disk library 108A.

Compliance copy rule set 164 is only associated with the email subclient 168, and not the file system subclient 166. Compliance copies generated according to compliance copy rule set 164 will therefore not include primary data 112A from the file system subclient 166. For instance, the organization may be under an obligation to store and maintain copies of email data for a particular period of time (e.g., 10 years) to comply with state or federal regulations, while similar regulations do not apply to file system data. Compliance copy rule set 164 is associated with the same tape library 108B and media agent 144B as disaster recovery copy rule set 162, although a different storage device or media agent could be used in other embodiments. Finally, compliance copy rule set 164 specifies that the copies it governs will be generated quarterly and retained for 10 years.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule set and being initiated at a point in time may be referred to as a “secondary copy job” (and sometimes may be called a “backup job,” even though it is not necessarily limited to creating only backup copies). Secondary copy jobs may be initiated on demand as well. Steps 1-9 below illustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backup job according to the backup copy rule set 160, which logically comprises all the secondary copy operations necessary to effectuate rules 160 in storage policy 148A every hour, including steps 1-4 occurring hourly. For instance, a scheduling service running on storage manager 140 accesses backup copy rule set 160 or a separate scheduling policy associated with client computing device 102 and initiates a backup job on an hourly basis. Thus, at the scheduled time, storage manager 140 sends instructions to client computing device 102 (i.e., to both data agent 142A and data agent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B on client computing device 102 respond to instructions from storage manager 140 by accessing and processing the respective subclient primary data 112A and 112B involved in the backup copy operation, which can be found in primary storage device 104. Because the secondary copy operation is a backup copy operation, the data agent(s) 142A, 142B may format the data into a backup format or otherwise process the data suitable for a backup copy.

At step 3, client computing device 102 communicates the processed file system data (e.g., using file system data agent 142A) and the processed email data (e.g., using email data agent 142B) to the first media agent 144A according to backup copy rule set 160, as directed by storage manager 140. Storage manager 140 may further keep a record in management database 146 of the association between media agent 144A and one or more of: client computing device 102, file system subclient 112A, file system data agent 142A, email subclient 112B, email data agent 142B, and/or backup copy 116A.

The target media agent 144A receives the data-agent-processed data from client computing device 102, and at step 4 generates and conveys backup copy 116A to disk library 108A to be stored as backup copy 116A, again at the direction of storage manager 140 and according to backup copy rule set 160. Media agent 144A can also update its index 153 to include data and/or metadata related to backup copy 116A, such as information indicating where the backup copy 116A resides on disk library 108A, where the email copy resides, where the file system copy resides, data and metadata for cache retrieval, etc. Storage manager 140 may similarly update its index 150 to include information relating to the secondary copy operation, such as information relating to the type of operation, a physical location associated with one or more copies created by the operation, the time the operation was performed, status information relating to the operation, the components involved in the operation, and the like. In some cases, storage manager 140 may update its index 150 to include some or all of the information stored in index 153 of media agent 144A. At this point, the backup job may be considered complete. After the 30-day retention period expires, storage manager 140 instructs media agent 144A to delete backup copy 116A from disk library 108A and indexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for a disaster recovery copy according to the disaster recovery rule set 162. Illustratively this includes steps 5-7 occurring daily for creating disaster recovery copy 116B. Illustratively, and by way of illustrating the scalable aspects and off-loading principles embedded in system 100, disaster recovery copy 116B is based on backup copy 116A and not on primary data 112A and 112B.

At step 6, illustratively based on instructions received from storage manager 140 at step 5, the specified media agent 1446 retrieves the most recent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and as specified in disaster recovery copy rule set 162, media agent 144B uses the retrieved data to create a disaster recovery copy 1166 and store it to tape library 1086. In some cases, disaster recovery copy 116B is a direct, mirror copy of backup copy 116A, and remains in the backup format. In other embodiments, disaster recovery copy 116B may be further compressed or encrypted, or may be generated in some other manner, such as by using primary data 112A and 1126 from primary storage device 104 as sources. The disaster recovery copy operation is initiated once a day and disaster recovery copies 1166 are deleted after 60 days; indexes 153 and/or 150 are updated accordingly when/after each information management operation is executed and/or completed. The present backup job may be considered completed.

At step 8, storage manager 140 initiates another backup job according to compliance rule set 164, which performs steps 8-9 quarterly to create compliance copy 116C. For instance, storage manager 140 instructs media agent 144B to create compliance copy 116C on tape library 1086, as specified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated using disaster recovery copy 1166 as the source. This is efficient, because disaster recovery copy resides on the same secondary storage device and thus no network resources are required to move the data. In other embodiments, compliance copy 116C is instead generated using primary data 112B corresponding to the email subclient or using backup copy 116A from disk library 108A as source data. As specified in the illustrated example, compliance copies 116C are created quarterly, and are deleted after ten years, and indexes 153 and/or 150 are kept up-to-date accordingly.

Example Applications of Storage Policies—Information Governance Policies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user to specify aspects of storage policy 148A. For example, the storage policy can be modified to include information governance policies to define how data should be managed in order to comply with a certain regulation or business objective. The various policies may be stored, for example, in management database 146. An information governance policy may align with one or more compliance tasks that are imposed by regulations or business requirements. Examples of information governance policies might include a Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery (e-discovery) policy, and so on.

Information governance policies allow administrators to obtain different perspectives on an organization's online and offline data, without the need for a dedicated data silo created solely for each different viewpoint. As described previously, the data storage systems herein build an index that reflects the contents of a distributed data set that spans numerous clients and storage devices, including both primary data and secondary copies, and online and offline copies. An organization may apply multiple information governance policies in a top-down manner over that unified data set and indexing schema in order to view and manipulate the data set through different lenses, each of which is adapted to a particular compliance or business goal. Thus, for example, by applying an e-discovery policy and a Sarbanes-Oxley policy, two different groups of users in an organization can conduct two very different analyses of the same underlying physical set of data/copies, which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy, which defines a taxonomy of classification terms or tags relevant to a compliance task and/or business objective. A classification policy may also associate a defined tag with a classification rule. A classification rule defines a particular combination of criteria, such as users who have created, accessed or modified a document or data object; file or application types; content or metadata keywords; clients or storage locations; dates of data creation and/or access; review status or other status within a workflow (e.g., reviewed or un-reviewed); modification times or types of modifications; and/or any other data attributes in any combination, without limitation. A classification rule may also be defined using other classification tags in the taxonomy. The various criteria used to define a classification rule may be combined in any suitable fashion, for example, via Boolean operators, to define a complex classification rule. As an example, an e-discovery classification policy might define a classification tag “privileged” that is associated with documents or data objects that (1) were created or modified by legal department staff, or (2) were sent to or received from outside counsel via email, or (3) contain one of the following keywords: “privileged” or “attorney” or “counsel,” or other like terms. Accordingly, all these documents or data objects will be classified as “privileged.”

One specific type of classification tag, which may be added to an index at the time of indexing, is an “entity tag.” An entity tag may be, for example, any content that matches a defined data mask format. Examples of entity tags might include, e.g., social security numbers (e.g., any numerical content matching the formatting mask XXX-XX-XXXX), credit card numbers (e.g., content having a 13-16 digit string of numbers), SKU numbers, product numbers, etc. A user may define a classification policy by indicating criteria, parameters or descriptors of the policy via a graphical user interface, such as a form or page with fields to be filled in, pull-down menus or entries allowing one or more of several options to be selected, buttons, sliders, hypertext links or other known user interface tools for receiving user input, etc. For example, a user may define certain entity tags, such as a particular product number or project ID. In some implementations, the classification policy can be implemented using cloud-based techniques. For example, the storage devices may be cloud storage devices, and the storage manager 140 may execute cloud service provider API over a network to classify data stored on cloud storage devices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restore operation can be initiated involving one or more of secondary copies 116A, 116B, and 116C. A restore operation logically takes a selected secondary copy 116, reverses the effects of the secondary copy operation that created it, and stores the restored data to primary storage where a client computing device 102 may properly access it as primary data. A media agent 144 and an appropriate data agent 142 (e.g., executing on the client computing device 102) perform the tasks needed to complete a restore operation. For example, data that was encrypted, compressed, and/or deduplicated in the creation of secondary copy 116 will be correspondingly rehydrated (reversing deduplication), uncompressed, and unencrypted into a format appropriate to primary data. Metadata stored within or associated with the secondary copy 116 may be used during the restore operation. In general, restored data should be indistinguishable from other primary data 112. Preferably, the restored data has fully regained the native format that may make it immediately usable by application 110.

As one example, a user may manually initiate a restore of backup copy 116A, e.g., by interacting with user interface 158 of storage manager 140 or with a web-based console with access to system 100. Storage manager 140 may accesses data in its index 150 and/or management database 146 (and/or the respective storage policy 148A) associated with the selected backup copy 116A to identify the appropriate media agent 144A and/or secondary storage device 108A where the secondary copy resides. The user may be presented with a representation (e.g., stub, thumbnail, listing, etc.) and metadata about the selected secondary copy, in order to determine whether this is the appropriate copy to be restored, e.g., date that the original primary data was created. Storage manager 140 will then instruct media agent 144A and an appropriate data agent 142 on the target client computing device 102 to restore secondary copy 116A to primary storage device 104. A media agent may be selected for use in the restore operation based on a load balancing algorithm, an availability based algorithm, or other criteria. The selected media agent, e.g., 144A, retrieves secondary copy 116A from disk library 108A. For instance, media agent 144A may access its index 153 to identify a location of backup copy 116A on disk library 108A, or may access location information residing on disk library 108A itself.

In some cases a backup copy 116A that was recently created or accessed, may be cached to speed up the restore operation. In such a case, media agent 144A accesses a cached version of backup copy 116A residing in index 153, without having to access disk library 108A for some or all of the data. Once it has retrieved backup copy 116A, the media agent 144A communicates the data to the requesting client computing device 102. Upon receipt, file system data agent 142A and email data agent 142B may unpack (e.g., restore from a backup format to the native application format) the data in backup copy 116A and restore the unpackaged data to primary storage device 104. In general, secondary copies 116 may be restored to the same volume or folder in primary storage device 104 from which the secondary copy was derived; to another storage location or client computing device 102; to shared storage, etc. In some cases, the data may be restored so that it may be used by an application 110 of a different version/vintage from the application that created the original primary data 112.

Example Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary depending on the embodiment. In some cases, secondary copies 116 are formatted as a series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4 GB, or 8 GB chunks). This can facilitate efficient communication and writing to secondary storage devices 108, e.g., according to resource availability. For example, a single secondary copy 116 may be written on a chunk-by-chunk basis to one or more secondary storage devices 108. In some cases, users can select different chunk sizes, e.g., to improve throughput to tape storage devices. Generally, each chunk can include a header and a payload. The payload can include files (or other data units) or subsets thereof included in the chunk, whereas the chunk header generally includes metadata relating to the chunk, some or all of which may be derived from the payload. For example, during a secondary copy operation, media agent 144, storage manager 140, or other component may divide files into chunks and generate headers for each chunk by processing the files. Headers can include a variety of information such as file and/or volume identifier(s), offset(s), and/or other information associated with the payload data items, a chunk sequence number, etc. Importantly, in addition to being stored with secondary copy 116 on secondary storage device 108, chunk headers can also be stored to index 153 of the associated media agent(s) 144 and/or to index 150 associated with storage manager 140. This can be useful for providing faster processing of secondary copies 116 during browsing, restores, or other operations. In some cases, once a chunk is successfully transferred to a secondary storage device 108, the secondary storage device 108 returns an indication of receipt, e.g., to media agent 144 and/or storage manager 140, which may update their respective indexes 153, 150 accordingly. During restore, chunks may be processed (e.g., by media agent 144) according to the information in the chunk header to reassemble the files.

Data can also be communicated within system 100 in data channels that connect client computing devices 102 to secondary storage devices 108. These data channels can be referred to as “data streams,” and multiple data streams can be employed to parallelize an information management operation, improving data transfer rate, among other advantages. Example data formatting techniques including techniques involving data streaming, chunking, and the use of other data structures in creating secondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086, and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171, respectively, which may be employed for performing information management operations. Referring to FIG. 1F, data agent 142 forms data stream 170 from source data associated with a client computing device 102 (e.g., primary data 112). Data stream 170 is composed of multiple pairs of stream header 172 and stream data (or stream payload) 174. Data streams 170 and 171 shown in the illustrated example are for a single-instanced storage operation, and a stream payload 174 therefore may include both deduplicated or single-instance (SI) data and/or non-SI data. A stream header 172 includes metadata about the stream payload 174. This metadata may include, for example, a length of the stream payload 174, an indication of whether the stream payload 174 is encrypted, an indication of whether the stream payload 174 is compressed, an archive file identifier (ID), an indication of whether the stream payload 174 is single instanceable (deduplicated), and an indication of whether the stream payload 174 is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 and stream payload 174 aligned into multiple data blocks. In this example, the data blocks are of size 64 KB. The first two stream header 172 and stream payload 174 pairs comprise a first data block of size 64 KB. The first stream header 172 indicates that the length of the succeeding stream payload 174 is 63 KB and that it is the start of a data block. The next stream header 172 indicates that the succeeding stream payload 174 has a length of 1 KB and that it is not the start of a new data block. Immediately following stream payload 174 is a pair comprising an identifier header 176 and identifier data 178. The identifier header 176 includes an indication that the succeeding identifier data 178 includes the identifier for the immediately previous data block. The identifier data 178 includes the identifier that the data agent 142 generated for the data block. The data stream 171 also includes other stream header 172 and stream payload 174 pairs, which may be for SI data and/or non-SI data.

FIG. 1H is a diagram illustrating data structures 180 that may be used to store blocks of SI (deduplicated) data and non-SI data on a storage device (e.g., secondary storage device 108). According to certain embodiments, data structures 180 do not form part of a native file system of the storage device. Data structures 180 include one or more volume folders 182, one or more chunk folders 184/185 within the volume folder 182, and multiple files within chunk folder 184. Each chunk folder 184/185 includes a metadata file 186/187, a metadata index file 188/189, one or more container files 190/191/193 (a/k/a “S-files” or “S-file containers”, and a container index file 192/194. Metadata file 186/187 stores non-SI data blocks as well as links to SI data blocks stored in container files. Metadata index file 188/189 stores an index to the data in the metadata file 186/187. Container files 190/191/193 store SI data blocks. Container index file 192/194 stores an index to container files 190/191/193. Among other things, container index file 192/194 stores an indication of whether a corresponding block in a container file 190/191/193 is referred to by a link in a metadata file 186/187. For example, data block B2 in the container file 190 is referred to by a link in metadata file 187 in chunk folder 185. Accordingly, the corresponding index entry in container index file 192 indicates that data block B2 in container file 190 is referred to. As another example, data block B1 in container file 191 is referred to by a link in metadata file 187, and so the corresponding index entry in container index file 192 indicates that this data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have been created as a result of separate secondary copy operations involving two client computing devices 102. For example, a first secondary copy operation on a first client computing device 102 could result in the creation of the first chunk folder 184, and a second secondary copy operation on a second client computing device 102 could result in the creation of the second chunk folder 185. Container files 190/191 in the first chunk folder 184 would contain the blocks of SI data of the first client computing device 102. If the two client computing devices 102 have substantially similar data, the second secondary copy operation on the data of the second client computing device 102 would result in media agent 144 storing primarily links to the data blocks of the first client computing device 102 that are already stored in the container files 190/191. Accordingly, while a first secondary copy operation may result in storing nearly all of the data subject to the operation, subsequent secondary storage operations involving similar data may result in substantial data storage space savings, because links to already stored data blocks can be stored instead of additional instances of data blocks.

If the operating system of the secondary storage computing device 106 on which media agent 144 operates supports sparse files, then when media agent 144 creates container files 190/191/193, it can create them as sparse files. A sparse file is a type of file that may include empty space (e.g., a sparse file may have real data within it, such as at the beginning of the file and/or at the end of the file, but may also have empty space in it that is not storing actual data, such as a contiguous range of bytes all having a value of zero). Having container files 190/191/193 be sparse files allows media agent 144 to free up space in container files 190/191/193 when blocks of data in container files 190/191/193 no longer need to be stored on the storage devices. In some examples, media agent 144 creates a new container file 190/191/193 when a container file 190/191/193 either includes 100 blocks of data or when the size of the container file 190 exceeds 50 MB. In other examples, media agent 144 creates a new container file 190/191/193 when a container file 190/191/193 satisfies other criteria (e.g., it contains from approx. 100 to approx. 1000 blocks or when its size exceeds approximately 50 MB to 1 GB). In some cases, a file on which a secondary copy operation is performed may comprise a large number of data blocks. For example, a 100 MB file may comprise 400 data blocks of size 256 KB. If such a file is to be stored, its data blocks may span more than one container file, or even more than one chunk folder. As another example, a database file of 20 GB may comprise over 40,000 data blocks of size 512 KB. If such a database file is to be stored, its data blocks will likely span multiple container files, multiple chunk folders, and potentially multiple volume folders. Restoring such files may require accessing multiple container files, chunk folders, and/or volume folders to obtain the requisite data blocks.

Using Backup Data for Replication and Disaster Recovery (“Live Synchronization”)

There is an increased demand to off-load resource intensive information management tasks (e.g., data replication tasks) away from production devices (e.g., physical or virtual client computing devices) in order to maximize production efficiency. At the same time, enterprises expect access to readily-available up-to-date recovery copies in the event of failure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and other issues by using backup or other secondary copy data to synchronize a source subsystem 201 (e.g., a production site) with a destination subsystem 203 (e.g., a failover site). Such a technique can be referred to as “live synchronization” and/or “live synchronization replication.” In the illustrated embodiment, the source client computing devices 202 a include one or more virtual machines (or “VMs”) executing on one or more corresponding VM host computers 205 a, though the source need not be virtualized. The destination site 203 may be at a location that is remote from the production site 201, or may be located in the same data center, without limitation. One or more of the production site 201 and destination site 203 may reside at data centers at known geographic locations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoing stream of incremental backups from the source subsystem 201 to the destination subsystem 203, such as according to what can be referred to as an “incremental forever” approach. FIG. 2A illustrates an embodiment of a data flow which may be orchestrated at the direction of one or more storage managers (not shown). At step 1, the source data agent(s) 242 a and source media agent(s) 244 a work together to write backup or other secondary copies of the primary data generated by the source client computing devices 202 a into the source secondary storage device(s) 208 a. At step 2, the backup/secondary copies are retrieved by the source media agent(s) 244 a from secondary storage. At step 3, source media agent(s) 244 a communicate the backup/secondary copies across a network to the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in an incremental fashion, such that only changed blocks are transmitted, and in some cases multiple incremental backups are consolidated at the source so that only the most current changed blocks are transmitted to and applied at the destination. An example of live synchronization of virtual machines using the “incremental forever” approach is found in U.S. Pat. No. 10,228,962 entitled “Live Synchronization and Management of Virtual Machines across Computing and Virtualization Platforms and Using Live Synchronization to Support Disaster Recovery.” Moreover, a deduplicated copy can be employed to further reduce network traffic from source to destination. For instance, the system can utilize the deduplicated copy techniques described in U.S. Pat. No. 9,239,687, entitled “Systems and Methods for Retaining and Using Data Block Signatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the received backup/secondary copy data to the destination secondary storage device(s) 208 b. At step 5, the synchronization is completed when the destination media agent(s) and destination data agent(s) 242 b restore the backup/secondary copy data to the destination client computing device(s) 202 b. The destination client computing device(s) 202 b may be kept “warm” awaiting activation in case failure is detected at the source. This synchronization/replication process can incorporate the techniques described in U.S. Patent Pub. No. 2016/0350391 entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis, the synchronized copies can be viewed as mirror or replication copies. Moreover, by applying the incremental backups to the destination site 203 using backup or other secondary copy data, the production site 201 is not burdened with the synchronization operations. Because the destination site 203 can be maintained in a synchronized “warm” state, the downtime for switching over from the production site 201 to the destination site 203 is substantially less than with a typical restore from secondary storage. Thus, the production site 201 may flexibly and efficiently fail over, with minimal downtime and with relatively up-to-date data, to a destination site 203, such as a cloud-based failover site. The destination site 203 can later be reverse synchronized back to the production site 201, such as after repairs have been implemented or after the failure has passed.

Integrating With the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful to provide data protection and other information management services in a scalable, transparent, and highly plug-able fashion. FIG. 2B illustrates an information management system 200 having an architecture that provides such advantages, and incorporates use of a standard file system protocol between primary and secondary storage subsystems 217, 218. As shown, the use of the network file system (NFS) protocol (or any another appropriate file system protocol such as that of the Common Internet File System (CIFS)) allows data agent 242 to be moved from the primary storage subsystem 217 to the secondary storage subsystem 218. For instance, as indicated by the dashed box 206 around data agent 242 and media agent 244, data agent 242 can co-reside with media agent 244 on the same server (e.g., a secondary storage computing device such as component 106), or in some other location in secondary storage subsystem 218.

Where NFS is used, for example, secondary storage subsystem 218 allocates an NFS network path to the client computing device 202 or to one or more target applications 210 running on client computing device 202. During a backup or other secondary copy operation, the client computing device 202 mounts the designated NFS path and writes data to that NFS path. The NFS path may be obtained from NFS path data 215 stored locally at the client computing device 202, and which may be a copy of or otherwise derived from NFS path data 219 stored in the secondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received by data agent 242 in secondary storage subsystem 218, which translates the requests and works in conjunction with media agent 244 to process and write data to a secondary storage device(s) 208, thereby creating a backup or other secondary copy. Storage manager 240 can include a pseudo-client manager 217, which coordinates the process by, among other things, communicating information relating to client computing device 202 and application 210 (e.g., application type, client computing device identifier, etc.) to data agent 242, obtaining appropriate NFS path data from the data agent 242 (e.g., NFS path information), and delivering such data to client computing device 202.

Conversely, during a restore or recovery operation client computing device 202 reads from the designated NFS network path, and the read request is translated by data agent 242. The data agent 242 then works with media agent 244 to retrieve, re-process (e.g., re-hydrate, decompress, decrypt), and forward the requested data to client computing device 202 using NFS.

By moving specialized software associated with system 200 such as data agent 242 off the client computing devices 202, the illustrative architecture effectively decouples the client computing devices 202 from the installed components of system 200, improving both scalability and plug-ability of system 200. Indeed, the secondary storage subsystem 218 in such environments can be treated simply as a read/write NFS target for primary storage subsystem 217, without the need for information management software to be installed on client computing devices 202. As one example, an enterprise implementing a cloud production computing environment can add VM client computing devices 202 without installing and configuring specialized information management software on these VMs. Rather, backups and restores are achieved transparently, where the new VMs simply write to and read from the designated NFS path. An example of integrating with the cloud using file system protocols or so-called “infinite backup” using NFS share is found in U.S. Patent Pub. No. 2017/0235647 entitled “Data Protection Operations Based on Network Path Information.” Examples of improved data restoration scenarios based on network-path information, including using stored backups effectively as primary data sources, may be found in U.S. Pat. No. 10,684,924 entitled “Data Restoration Operations Based on Network Path Information.”

Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often from various applications running in geographically distributed locations. FIG. 2C shows a block diagram of an example of a highly scalable, managed data pool architecture useful in accommodating such data growth. The illustrated system 200, which may be referred to as a “web-scale” architecture according to certain embodiments, can be readily incorporated into both open compute/storage and common-cloud architectures.

The illustrated system 200 includes a grid 245 of media agents 244 logically organized into a control tier 231 and a secondary or storage tier 233. Media agents assigned to the storage tier 233 can be configured to manage a secondary storage pool 208 as a deduplication store, and be configured to receive client write and read requests from the primary storage subsystem 217, and direct those requests to the secondary tier 233 for servicing. For instance, media agents CMA1-CMA3 in the control tier 231 maintain and consult one or more deduplication databases 247, which can include deduplication information (e.g., data block hashes, data block links, file containers for deduplicated files, etc.) sufficient to read deduplicated files from secondary storage pool 208 and write deduplicated files to secondary storage pool 208. For instance, system 200 can incorporate any of the deduplication systems and methods shown and described in U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated Storage System,” and U.S. Pat. No. 9,633,033 entitled “High Availability Distributed Deduplicated Storage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive write and read requests from media agents CMA1-CMA3 in control tier 231, and access secondary storage pool 208 to service those requests. Media agents CMA1-CMA3 in control tier 231 can also communicate with secondary storage pool 208, and may execute read and write requests themselves (e.g., in response to requests from other control media agents CMA1-CMA3) in addition to issuing requests to media agents in secondary tier 233. Moreover, while shown as separate from the secondary storage pool 208, deduplication database(s) 247 can in some cases reside in storage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6, etc.) in grid 245 can be allocated a corresponding dedicated partition 251A-2511, respectively, in secondary storage pool 208. Each partition 251 can include a first portion 253 containing data associated with (e.g., stored by) media agent 244 corresponding to the respective partition 251. System 200 can also implement a desired level of replication, thereby providing redundancy in the event of a failure of a media agent 244 in grid 245. Along these lines, each partition 251 can further include a second portion 255 storing one or more replication copies of the data associated with one or more other media agents 244 in the grid.

System 200 can also be configured to allow for seamless addition of media agents 244 to grid 245 via automatic configuration. As one illustrative example, a storage manager (not shown) or other appropriate component may determine that it is appropriate to add an additional node to control tier 231, and perform some or all of the following: (i) assess the capabilities of a newly added or otherwise available computing device as satisfying a minimum criteria to be configured as or hosting a media agent in control tier 231; (ii) confirm that a sufficient amount of the appropriate type of storage exists to support an additional node in control tier 231 (e.g., enough disk drive capacity exists in storage pool 208 to support an additional deduplication database 247); (iii) install appropriate media agent software on the computing device and configure the computing device according to a pre-determined template; (iv) establish a partition 251 in the storage pool 208 dedicated to the newly established media agent 244; and (v) build any appropriate data structures (e.g., an instance of deduplication database 247). An example of highly scalable managed data pool architecture or so-called web-scale architecture for storage and data management is found in U.S. Pat. No. 10,255,143 entitled “Deduplication Replication In A Distributed Deduplication Data Storage System.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and 2C, as well as those in FIGS. 1A-1H, may be implemented in any combination and permutation to satisfy data storage management and information management needs at one or more locations and/or data centers.

Cloud Computing. The National Institute of Standards and Technology (NIST) provides the following definition of Cloud Computing characteristics, service models, and deployment models:

Cloud Computing

-   -   Cloud computing is a model for enabling ubiquitous, convenient,         on-demand network access to a shared pool of configurable         computing resources (e.g., networks, servers, storage,         applications, and services) that can be rapidly provisioned and         released with minimal management effort or service provider         interaction. This cloud model is composed of five essential         characteristics, three service models, and four deployment         models.

Essential Characteristics:

-   -   On-demand self-service. A consumer can unilaterally provision         computing capabilities, such as server time and network storage,         as needed automatically without requiring human interaction with         each service provider.     -   Broad network access. Capabilities are available over the         network and accessed through standard mechanisms that promote         use by heterogeneous thin or thick client platforms (e.g.,         mobile phones, tablets, laptops, and workstations).     -   Resource pooling. The provider's computing resources are pooled         to serve multiple consumers using a multi-tenant model, with         different physical and virtual resources dynamically assigned         and reassigned according to consumer demand. There is a sense of         location independence in that the customer generally has no         control or knowledge over the exact location of the provided         resources but may be able to specify location at a higher level         of abstraction (e.g., country, state, or datacenter). Examples         of resources include storage, processing, memory, and network         bandwidth.     -   Rapid elasticity. Capabilities can be elastically provisioned         and released, in some cases automatically, to scale rapidly         outward and inward commensurate with demand. To the consumer,         the capabilities available for provisioning often appear to be         unlimited and can be appropriated in any quantity at any time.     -   Measured service. Cloud systems automatically control and         optimize resource use by leveraging a metering capability¹ at         some level of abstraction appropriate to the type of service         (e.g., storage, processing, bandwidth, and active user         accounts). Resource usage can be monitored, controlled, and         reported, providing transparency for both the provider and         consumer of the utilized service. ¹ Typically this is done on a         pay-per-use or charge-per-use basis.

Service Models:

-   -   Software as a Service (SaaS). The capability provided to the         consumer is to use the provider's applications running on a         cloud infrastructure². The applications are accessible from         various client devices through either a thin client interface,         such as a web browser (e.g., web-based email), or a program         interface. The consumer does not manage or control the         underlying cloud infrastructure including network, servers,         operating systems, storage, or even individual application         capabilities, with the possible exception of limited         user-specific application configuration settings. ² A cloud         infrastructure is the collection of hardware and software that         enables the five essential characteristics of cloud computing.         The cloud infrastructure can be viewed as containing both a         physical layer and an abstraction layer. The physical layer         consists of the hardware resources that are necessary to support         the cloud services being provided, and typically includes         server, storage and network components. The abstraction layer         consists of the software deployed across the physical layer,         which manifests the essential cloud characteristics.         Conceptually the abstraction layer sits above the physical         layer.     -   Platform as a Service (PaaS). The capability provided to the         consumer is to deploy onto the cloud infrastructure         consumer-created or acquired applications created using         programming languages, libraries, services, and tools supported         by the provider.³ The consumer does not manage or control the         underlying cloud infrastructure including network, servers,         operating systems, or storage, but has control over the deployed         applications and possibly configuration settings for the         application-hosting environment. ³ This capability does not         necessarily preclude the use of compatible programming         languages, libraries, services, and tools from other sources.     -   Infrastructure as a Service (IaaS). The capability provided to         the consumer is to provision processing, storage, networks, and         other fundamental computing resources where the consumer is able         to deploy and run arbitrary software, which can include         operating systems and applications. The consumer does not manage         or control the underlying cloud infrastructure but has control         over operating systems, storage, and deployed applications; and         possibly limited control of select networking components (e.g.,         host firewalls).

Deployment Models:

-   -   Private cloud. The cloud infrastructure is provisioned for         exclusive use by a single organization comprising multiple         consumers (e.g., business units). It may be owned, managed, and         operated by the organization, a third party, or some combination         of them, and it may exist on or off premises.     -   Community cloud. The cloud infrastructure is provisioned for         exclusive use by a specific community of consumers from         organizations that have shared concerns (e.g., mission, security         requirements, policy, and compliance considerations). It may be         owned, managed, and operated by one or more of the organizations         in the community, a third party, or some combination of them,         and it may exist on or off premises.     -   Public cloud. The cloud infrastructure is provisioned for open         use by the general public. It may be owned, managed, and         operated by a business, academic, or government organization, or         some combination of them. It exists on the premises of the cloud         provider.     -   Hybrid cloud. The cloud infrastructure is a composition of two         or more distinct cloud infrastructures (private, community, or         public) that remain unique entities, but are bound together by         standardized or proprietary technology that enables data and         application portability (e.g., cloud bursting for load balancing         between clouds).

Source: Peter MeII, Timothy Grance (September 2011). The NIST Definition of Cloud Computing, National Institute of Standards and Technology: U.S. Department of Commerce. Special publication 800-145. nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf (accessed 26 Apr. 2019). Cloud computing aims to allow those who consume the services (whether individuals or organizations) to benefit from the available technologies without the need for deep knowledge about or expertise with each of them. Wikipedia, Cloud Computing, en.wikipedia.org/wiki/Cloud computing (accessed 26 Apr. 2019). “Cloud computing metaphor: the group of networked elements providing services need not be individually addressed or managed by users; instead, the entire provider-managed suite of hardware and software can be thought of as an amorphous cloud.” Id.

Cloud Service Accounts and Variability in Cloud Services. Cloud service providers such as Amazon, Microsoft, Alibaba, Google, Salesforce, Cisco, etc. provide access to their particular cloud services via cloud service accounts, such as corporate accounts, departmental accounts, individual user accounts, etc. Each cloud service account typically has authentication features, e.g., passwords, certificates, etc., to restrict and control access to the cloud service. Each account also might have service level guarantees and/or other terms and conditions between the cloud service provider and the service subscriber, e.g., a company, a government agency, an individual user. A subscribing entity might have multiple accounts with a cloud service provider, such as an account for the Engineering department, an account for the Finance department, an account for the Human Resources department, other accounts for individual company users, etc., without limitation. Each cloud service account carries different authentication, even though the services subscriber is the same entity. Different cloud service accounts might differ not just in service level guarantees, but might include different services. For example, one account might include long-term storage resources, whereas another account might be limited to ordinary data storage. For example, some accounts might have access to data processing functions supplied by the cloud service provider, such as machine learning algorithms, statistical analysis packages, etc., whereas other accounts might lack such features. Accordingly, the resources available to the user(s) of cloud service accounts can vary as between accounts, even if the accounts have the same subscriber and the same cloud service provider. Thus, the user experience and the technologies available as between cloud service accounts can vary significantly. Thus, when considering cloud computing, the specifics of cloud service accounts can play a role in the availability and/or portability of resources. Crossing account boundaries can pose technological barriers when considering migration of applications and their cloud services assets.

Cloud Availability Zones. “Availability zones (AZs) are isolated locations within . . . regions from which public cloud services originate and operate. Regions are geographic locations in which public cloud service providers' data centers reside. Businesses choose one or multiple worldwide availability zones for their services depending on business needs. Businesses select availability zones for a variety of reasons, including compliance and proximity to end customers. Cloud administrators can also choose to replicate services across multiple availability zones to decrease latency or protect resources. Admins can move resources to another availability zone in the event of an outage. Certain cloud services may also be limited to particular regions or AZs.” Source: Margaret Rouse, Definition of Availability Zones, TechTarget, searchaws.techtarget.com/definition/availability-zones (accessed 26 Apr. 2019). Here is a vendor-specific example of how cloud service availability zones are organized in the Google Cloud: “Certain [Google] Compute Engine resources live in regions or zones. A region is a specific geographical location where you can run your resources. Each region has one or more zones; most regions have three or more zones. For example, the us-central1 region denotes a region in the Central United States that has zones us-central1-a, us-central1-b, us-central1-c, and us-central1-f. Resources that live in a zone, such as instances or persistent disks, are referred to as zonal resources. Other resources, like static external IP addresses, are regional. Regional resources can be used by any resources in that region, regardless of zone, while zonal resources can only be used by other resources in the same zone. For example, disks and instances are both zonal resources. To attach a disk to an instance, both resources must be in the same zone. Similarly, if you want to assign a static IP address to an instance, the instance must be in the same region as the static IP. Only certain resources are region- or zone-specific. Other resources, such as images, are global resources that can be used by any other resources across any location. For information on global, regional, and zonal Compute Engine resources, see Global, Regional, and Zonal Resources.” Source: Google Cloud Regions and Zones, cloud.google.com/compute/docs/regions-zones/ (accessed 26 Apr. 2019) (emphasis added). Accordingly, when considering cloud computing, availability zones can play a role in the availability and/or portability of resources. Crossing zone boundaries can pose technological barriers when considering migration of applications and their cloud service assets, even when the different availability zones are supplied by the same cloud service provider.

Traditional Non-Cloud (“On-Premises”) Data Centers are Distinguishable from Cloud Computing. Traditional data centers generally do not have cloud computing characteristics. For example, the user experience is generally different, for example in regard to the name space(s) used for the storage, computing, and network resources. Moreover, substantial increases in resources needed by a user are not provisioned on demand. A traditional data center is physically located within the enterprise/organization that owns it. A traditional non-cloud data center might comprise computing resources such as servers, mainframes, virtual servers/clusters, etc.; and/or data storage resources, such as network-attached storage, storage area networks, tape libraries, etc. The owner of the traditional data center procures hardware, software, and network infrastructure (including making the associated capital investments); and manages going-forward planning for the data center. A traditional data center is staffed by professional Information Technology (IT) personnel, who are responsible for the data center's configuration, operation, upgrades, and maintenance. Thus, a traditional non-cloud data center can be thought of as self-managed by its owner/operator for the benefit of in-house users, as compared to cloud computing, which is managed by the cloud service provider and supplied as a service to outside subscribers. Clearly, a cloud computing service also has hardware, software, and networking infrastructure and professionals staffing it, as well as having an owner responsible for housing and paying for the infrastructure. However, the cloud computing service is consumed differently, served differently, and deployed differently compared to non-cloud data centers. Traditional non-cloud data centers are sometimes referred to as “on-premises” data centers, because their facilities are literally within the bounds of the organization that owns the data center. Cloud service providers' data centers generally are not within the bounds of the subscriber organization and are consumed “at a distance” “in the cloud.”

Accordingly, when considering cloud computing versus non-cloud data center deployment, the choice can play a role in the availability and/or portability of resources. Crossing boundaries between non-cloud data centers and cloud computing can pose technological barriers. For example, storing a database at a non-cloud data center might require different resources and/or access features/controls than storing the database at a cloud computing service. Thus, moving the database from the non-cloud data center to a cloud service account may require data conversion, re-configuration, and/or adaptation that go above and beyond merely copying the database. Likewise for virtual machines (VMs), as hypervisors available on-premises may be different from cloud-native hypervisors. Conversely, moving data, applications, VMs, and/or web services from cloud computing to a non-cloud data center also can involve data conversion, re-configuration, and/or adaptation to ensure success.

Systems and Methods for Optimizing Storage and Retention of Deduplicated Secondary Copies at Storage Platforms that are Write-Once Read-Many (Worm) Enabled

A WORM-enabled storage platform as referenced herein may be implemented in a cloud computing environment or in a non-cloud data center using storage arrays or other data storage devices, without limitation.

FIGS. 3A-3B depict block diagrams illustrating some salient portions of a system 300 for optimizing the storing and retention of deduplicated secondary copies at storage platforms that are bucket-level write-once read-many (WORM) enabled, according to an illustrative embodiment. Enhancements include without limitation: user interface (UI) options to enable WORM functionality for secondary storage, whether used for deduplicated or non-deduplicated secondary copies; enhancements to secondary copy operations; pruning changes; and media agent support for APIs and/or other communication protocols for communicating with WORM-enabled storage platforms to implement the features disclosed herein.

In regard to the UI, when a user activates or enables the WORM option, the illustrative system configures various entities, components, and resources without requiring further input from users, e.g., making the storage library is WORM-enabled; computing a DDB sealing frequency based on user-selected retention criteria, and setting the DDB for perioding sealing; computing a WORM lock 399/499 based on copy retention and seal frequency, and establishing the WORM lock retention on the storage resources; and marking the storage library to follow macro-pruning rules, which among other things, delete only those secondary copies that are based on a sealed DDB after the retention days criterion is satisfied. See also FIGS. 13 and 14 . In regard to secondary copy operations (e.g., deduplication copy jobs, backups) targeted to object-level WORM storage, the system is enhanced to determine (e.g., by the storage manager) a WORM expiry time (e.g., 499) that is based on copy retention time, DDB seal frequency, and DDB creation time, and send the WORM expiry time to the media agent responsible for interfacing with the WORM storage; set (e.g., by the media agent) the WORM expiry time on objects created as secondary copies. See also FIG. 10 . In regard to secondary copy operations targeted to bucket-level WORM storage, the system is enhanced to maintain at the storage manager and/or management database a last-chunk close time for every volume folder. See also FIG. 9 . In regard to pruning secondary copies from object-level WORM storage, the system (e.g., the storage manager, the media agent) is enhanced to initiate pruning for all secondary copies that are based on a certain sealed DDB once all jobs (and secondary copies generated by those jobs) have aged. In regard to pruning secondary copies from bucket-level WORM storage, the system is enhanced to initiate pruning for all objects in a volume folder once all jobs (and secondary copies generated by those jobs) have aged based on the last-chunk close time tracked for every volume folder. See also FIG. 12 .

FIG. 3A depicts: client computing device 102 hosting data agent 142; data storage device 104 comprising primary data 112; media agent host computing device 106 hosting media agent 344; storage manager host computing device 304 hosting storage manager 340; media agent host computing device 306 hosting media agent 345 and a first deduplication database (DDB1) 346-1; and storage platform 350 comprising deduplicated secondary copies 116-1, which are created based on DDB1. Bucket-level Worm lock duration 399 is applied to deduplicated secondary copies 116-1. A logical view of communication pathways for communication signaling, reporting, and/or instructions between components is depicted by the dotted bi-directional arrows, including arrows 395 and 396, which facilitate use of DDB1 346-1. A logical view of data pathways from primary data 112 to secondary copies 116-1 is depicted by the bold unidirectional arrows. FIG. 3B depicts the same components as FIG. 3A and additionally depicts: DDB1 346-1 being sealed, inactive/deactivated, and/or deleted; deduplicated secondary copies 116-1 marked for pruning and/or deleted; DDB2 346-2 operating as the active DDB at computing device 306; and deduplicated secondary copies 116-2 (created based on DDB2) at storage platform 350. The data pathways go from primary data 112 to deduplicated secondary copies 116-2. Bucket-level WORM lock duration 399 is applied to deduplicated secondary copies 116-2. FIG. 3B may be understood to depict a point in time after the configuration of FIG. 3A.

System 300 is a data storage management system similar to system 100 and additionally enhanced for optimizing storage and retention of deduplicated secondary copies at storage platforms that are WORM enabled. System 300 comprises storage manager 340, data agent 142, media agents 344 and 345, DDB1 346-1, and DDB2 346-2. System 300 generates deduplicated secondary copies 116-1 and 116-2, based on using DDB1 and DDB2, respectively. Storage platform 350, data storage device 104, and computing devices 102, 304, and 306 need not be part of system 300, but some or all of these components may be included in some embodiments of system 300. System 300 may further comprise other components described in the preceding figures, without limitation.

Client computing device 102, data storage device 104, media agent host computing device (a/k/a secondary storage computing device) 106, primary data 112, and data agent 142 are described in more detail elsewhere herein.

Deduplicated secondary copies 116 (e.g., 116-1, 116-2). Deduplicated secondary copies 116-1 are secondary copies generated by system 300 with deduplication or single-instancing. Deduplicated secondary copies 116-1 are generated by jobs (e.g., deduplication copy jobs) that are associated with or are based on DDB1 346-1, because the deduplication operations use DDB1 for signature lookups. Thus, deduplicated secondary copies 116-1 are associated with or based on DDB1. Deduplicated secondary copies 116-1 may be any one or more of backup copies, archive copies, auxiliary copies, reference copies, etc., without limitation, and/or full copies, incremental copies, differential copies, or any combination thereof, without limitation. Deduplicated secondary copies 116-2 are secondary copies generated by system 300 with deduplication or single-instancing. Deduplicated secondary copies 116-2 are generated by jobs (e.g., deduplication copy jobs) that are associated with or are based on DDB2 346-2, because the deduplication operations use DDB2 for signature lookups, not DDB1. Thus, deduplicated secondary copies 116-2 are associated with or based on DDB2. Deduplicated secondary copies 116-2 may be any one or more of backup copies, archive copies, auxiliary copies, reference copies, etc., without limitation, and/or full copies, incremental copies, differential copies, or any combination thereof, without limitation. Deduplicated secondary copies 116-2 may co-exist with deduplicated secondary copies 116-1 for at least some time after DDB1 is sealed.

Storage manager host computing device 304 is a computing device comprising one or more hardware processors and computer memory for executing programming instructions. Depending on the implementation of system 300, computing device 304 may be implemented in a cloud computing environment or in a non-cloud data center, without limitation. Computing device 304 hosts storage manager 340.

Media agent host computing device (a/k/a secondary storage computing device) 306 is a computing device comprising one or more hardware processors and computer memory for executing programming instructions. Depending on the implementation of system 300, computing device 306 may be implemented in a cloud computing environment or in a non-cloud data center, without limitation. Computing device 306 hosts media agent 345 and any number of DDBs (e.g., DDB1 346-1, DDB2 346-2, etc.). Preferably, computing device 306 comprises solid-state drive (SSD) technology as the storage medium for each DDB, so that the DDB may provide faster lookups than ordinary spinning disk storage. SSD technology is well known in the art. Each DDB occupies one or more SSDs, without limitation.

Storage manager 340 is analogous to storage manager 140 and is additionally enhanced for operating in system 300. Enhancements include native configuration features and an associated user interface that enable users to set up storage preferences and deduplication jobs targeted to WORM-enabled data storage, and to specify relevant parameters such as retention periods and/or DDB sealing intervals, which are used by system 300 to implement the disclosed features. Storage manager 340 is additionally enhanced with other features that manage storage and retention of deduplicated secondary copies 116 at WORM-enabled storage platforms. More details are given in subsequent figures, including in FIG. 13 .

Media agent 344 is analogous to media agent 144 and is additionally enhanced for operating within system 300. Enhancements include features for communicating with one or more storage platforms 350 via a platform-specific application programming interface (API) or via another suitable electronic communication protocol. The API/protocol is used for transmitting instructions to and/or requesting information from storage platform 350, and may include any number of storage-related configurations and/or features, such as creating new storage buckets, transmitting WORM lock parameters, obtaining WORM lock status, etc., without limitation. Media agent 344 is additionally tasked with generating deduplicated secondary copies 116-1, 116-2, etc. and storing them in appropriate locations and/or storage buckets at storage platform 350. In a restore operation, media agent 344 retrieves secondary copies 116 from storage platform 350 and in conjunction with data agent 142 (or another data agent) transforms the secondary copy data from a backup format into a primary data format that is natively accessible to an application with access to data storage device 104. Media agent 344 uses communication pathway 396 to communicate with the active DDB (e.g., DDB1 346-1, DDB2 346-2, etc.), if necessary, to deduplicate data being backed up.

Media agent 345 is analogous to media agent 144 and is specially configured for providing access to/from the currently active DDB (e.g., DDB1 346-1 in FIGS. 3A and 4A, DDB2 346-2 in FIGS. 3B and 4B, etc.) and is further tasked with: sealing each DDB at certain intervals (the DDB seal frequency 502), setting up a new active DDB, and ultimately deleting the sealed DDB. Preferably, no more than one sealed DDB is retained after a new DDB is activated, though the invention is not so limited. In some embodiments, storage manager 340 instructs media agent 345 to seal an active DDB, open up a new active DDB, and delete the sealed DDB(s). In other embodiments, media agent 345 self-manages these operations after receiving initial instruction(s) and DDB seal frequency 502 from storage manager 340, e.g., when a user configures storage policies and storage pools for certain primary data sources (subclients). In some configurations, the functions of media agent 344 and media agent 345 are performed by the same media agent 344/345 operating on a single computing device or compute resource, rather than by distinct media agents running on distinct computing devices.

Deduplication database DDB 346 (e.g., 346-1, 346-2). First deduplication database (DDB1) 346-1 is a data structure that stores unique signatures or identifiers of data portions (e.g., data blocks) that have been written into a deduplicated secondary copy 116 since DDB1 was activated. More details on deduplication or single-instancing (SI) can be found in the section entitled Deduplication/Single-Instancing Operations and in the text accompanying FIG. 1H. According to the illustrative embodiments, only one DDB is active at any given time, and therefore signature lookups are addressed to one and only one DDB, i.e., to the active DDB. Any previously created and sealed DDB is not used for lookups after being sealed. Thus, a data block being considered for deduplication is treated as new if its signature is not found in the active DDB, even though it may have a signature in a sealed DDB. Even though the sealed DDB may still be present on computing device 306, once it is sealed, that DDB is no longer used by system 300 according to the illustrative embodiments. DDB1 346-1 is the active DDB in FIGS. 3A and 4A, but has been sealed and is inactive in FIGS. 3B and 4B. The deduplication secondary copy jobs that generate deduplicated secondary copies 116-1 are said to be associated with or based on DDB1. Correspondingly, deduplication copy jobs that generate deduplicated secondary copies 116-2 are associated with DDB2. And so on, as each active DDBs is sealed and a new one activated according to the DDB sealing frequency 502. Second deduplication database (DDB2) 346-2, which is similar to DDB1, is a data structure that stores unique signatures or identifiers of data portions (e.g., data blocks) that have been written into a deduplicated secondary copy 116 since DDB2 was activated. DDB2 346-2 is the active DDB in FIGS. 3B and 4B. Although the present figures depicts only two DDBs (DDB1 and DDB2), system 300 has no such limitation, and any number of successive DDBs may be sealed and followed by a new active DDB.

Storage platform 350 is data storage hardware that is used as a target for storing deduplicated secondary copies 116 generated by system 300. Storage platform 350 is WORM-enabled. WORM-enabled data storage typically has the agency and capability to enforce WORM locks on the data stored therein. Thus, once written to storage platform 350, deduplicated secondary copies 116 cannot be deleted or modified for as long as storage platform 350 has a WORM lock thereon. This write protection ensures that secondary copies 116 cannot be tampered with while the WORM lock (or WORM hold) is in force. WORM technologies prevent rewrites at the physical disk level, which cannot be modified or overridden by the computers that write or read the stored data, e.g., by media agents 344, by users, by bad actors gaining access to storage platform 350, etc. Storage platform 350 may be implemented as a storage array in a non-cloud data center or as a cloud-based data storage resource in a cloud computing environment, without limitation. Some vendors, cloud service providers, and/or managed service providers limit their storage platform 350 to one of either bucket-level enforcement or object-level WORM enforcement, which in turn requires system 300 to adapt its configuration settings accordingly. Bucket-level WORM lock generally operates by applying a certain duration (e.g., WORM lock duration 399) to every object stored in the target data storage bucket based on the creation time of each data object. Thus, every data object receives the same WORM lock duration 399 when it is stored at storage platform 350, meaning that the expiry time of the WORM lock “slides” forward as new objects with later creation times are stored. Object-level WORM lock enables a fixed WORM lock expiry time 499 to be implemented for data objects in a certain bucket, e.g., by enforcing a given expiry time or by enforcing progressively shorter remaining WORM lock times, so that ultimately all the data objects may be released from the WORM lock at substantially the same time (e.g., 499), in contrast to the sliding window of bucket-level hold. There may be other combinations or permutations of bucket-level and object-level WORM locking. System 300 adapts accordingly.

Arrows 395 and 396 depict communication pathways between components of system 300, and they represent alternative embodiments used for client-side deduplication and target-side deduplication, respectively. See also the section entitled Deduplication/Single-Instancing Operations. To generate deduplicated secondary copies, data agent 142 and/or media agent 344 needs to communicate with the active DDB (e.g., DDB1 346-1, DDB2 346-2, etc.) to look up a data block signature and determine whether a certain data block is new or can be referenced instead. Communication pathways 395 or 396, respectively, are used for that purpose. In FIGS. 3A and 4A, deduplication operations are based on lookups in DDB1, whereas in FIGS. 3B and 4B, deduplication operations are based on lookups in DDB2.

Bucket-level WORM lock duration 399 is applied to deduplicated secondary copies 116-1 and 116-2 in a storage platform 350 that has bucket-level WORM storage. See also FIGS. 5A-5B.

FIG. 3C is a block diagram illustrating how system 300 organizes deduplicated secondary copies 116 in volume folders 182 configured in a bucket at a WORM-enabled storage platform 350, according to an illustrative embodiment. All the items depicted here are described in more detail elsewhere herein, e.g., in the section entitled Deduplication/Single-Instancing Operations and in the text accompanying FIG. 1H. The present figure is included here to provide a graphical illustration of how deduplicated secondary copies 116 (e.g., 116-1, 116-2), are organized by deduplication copy jobs in system 300. Thus, illustratively, each deduplication copy job (1, 2 . . . J) generates backup data organized into files and folders, the highest level folder for each job being a so-called volume folder 182 (e.g., 182-1, 182-2 . . . 182-J). Each volume folder comprises one or more (1 . . . M) so-called chunk folders 184 or 185. Each chunk folder 184/185 (e.g., 184/185-1 . . . 184/185-M) comprises one or more of: metadata file 186/187; metadata index file 188/189; S-files (or S-file containers) 190/191/193; and container index file 192/194. See also FIG. 1H. As described in further detail in other figures, WORM locks are enforced by storage platform 350 according to timetables or time parameters supplied by system 300.

FIGS. 4A-4B depict block diagrams illustrating portions of system 300 configured for optimizing the storing and retention of deduplicated secondary copies at storage platforms that are object-level WORM-enabled, according to an illustrative embodiment. FIG. 4A depicts the same components and general arrangement as FIG. 3A, but is distinguishable because storage platform 450 enforces distinct WORM locks at the object level rather than bucket-level. For example, a WORM lock expiry time 499-1 (or an equivalent diminishing retention time period 550) is enforced for every object stored, resulting in the WORM lock being lifted at substantially the same time for all the affected data objects, e.g., volume folders 182, chunk folders 184/185, files 186-194, etc.

A logical view of data pathways from primary data 112 to secondary copies 116-1 comprising volume folders 182, chunk folders 184/185, files 186-194, etc. is depicted by the bold unidirectional arrows. FIG. 4B depicts the same components as those shown in FIG. 4A and additionally depicts: DDB1 346-1 is sealed, inactive/deactivated, and/or deleted; deduplicated secondary copies 116-1 are marked for pruning and/or deleted; DDB2 346-2 operating as the active DDB at computing device 306; and deduplicated secondary copies 116-2 at storage platform 350. The signaling pathways involve DDB2 346-2 instead of DDB1 346-1. Object-level WORM expiry time 499-2 (or an equivalent diminishing retention time period 550) is applied to deduplicated secondary copies 116-2. FIG. 4B may be understood to depict a point in time after the configuration of FIG. 4A, and correspondingly, WORM expiry time 499-2 is later than 499-1. With each sealing of a DDB and activation of a new DDB, a new object-level WORM expiry time 499 is calculated and applied to deduplicated secondary copies associated with the new DDB, e.g., 499-3, 499-4, etc.

FIG. 5A depicts bucket-level WORM handling of deduplicated secondary copies according to an example in the prior art. The present figure illustrates certain timing parameters related to WORM locks and depicts an illustrative timetable of how deduplicated secondary copies 116 associated with DDB1 and DDB2 may be handled by the prior art. A copy retention period 501 for backup data (secondary copies 116 based on primary data 112) is configured as 30 days, e.g., in a storage policy that specifies storage platform 350 as the storage destination. The same amount of time (e.g., 30 days) is assigned to the DDB seal frequency 502. For a bucket-level WORM-enabled storage platform 350 (specified as a storage pool), a WORM lock duration 399 is defined as the sum of the copy retention period 501 and the DDB seal frequency 502, e.g., 30 d+30 d=60 d. The corresponding WORM expiry time 503 for any given data object will be a sliding figure, not fixed.

Each row of the larger table in the present figure represents a distinct calendar day. Column 510 indicates whether the currently active DDB is sealed on the given day. Column 512 indicates which DDB is currently active. Column 514 indicates the calendar day when the backup data (deduplicated secondary copy 116) is created and stored in storage platform 350. Column 516 identifies, by way of a job ID, the deduplication copy job on that day; the job corresponds to the data objects created by the job, i.e., deduplicated secondary copy(ies) 116. Column 518 calculates when the governing WORM lock duration 399 will expire for that job and corresponding secondary copies 116, i.e., date of creation+WORM lock duration. Column 520 indicates when, in the prior art, the jobs associated with the respective DDB become eligible to be pruned from storage platform 350. For example, a job that runs on day 1 based on DDB 1 creates deduplicated secondary copies 116-1 that require a 60-day WORM lock, which expires on day 61. The 60-day WORM lock for day-2 jobs expires on day 62, and so on, until day 30 when DDB1 is sealed. The 60-day WORM lock for day-30 jobs expires on day 90. Because DDB1 is sealed on day 30, and DDB2 becomes the active DDB, the cycle starts anew on day 31. Column 522 indicates how many days the job/copies reside on storage platform 350 before they are eligible for pruning, e.g., ranging from 60 to as many as 90 days.

Thus, according to this example, the day-1 jobs/copies remain in storage for 90 days, whereas the day-30 jobs remain for 60 days. Because day-30 jobs may need to reference original data blocks in earlier secondary copies, as early as day-1 copies, all deduplicated secondary copies 116-1 associated with DDB1 are retained until the WORM lock expires on the last of those jobs, i.e., a day-90 expiry for the day-30 secondary copies. Thus, at day 90, in the prior-art, a pruning job marks all the DDB1-related secondary copies 116-1 as eligible for deletion, and a media agent 144 will delete those copies in due time from storage platform 350. The result is that for a given DDB, using the timing parameters and rules depicted in the present figure, a deduplicated secondary copy 116 will reside in storage platform 350 for an average of ½(60+90)=75 days.

FIG. 5B depicts bucket-level WORM handling of deduplicated secondary copies in system 300, according to an illustrative embodiment. The scenarios depicted here correspond to FIGS. 3A and 3B, i.e., enhanced data storage management of bucket-level WORM-enabled storage. The timing parameters 501, 502, and 399 of the top table in the present figure remain the same as those depicted in FIG. 5A, but the depicted timetable is different. Columns 510-516 and 522 represent the same kind of information as those depicted in FIG. 5A. Column 530 lists the volume folders 182 created for each new job according to some embodiments. Column 532 calculates when the governing bucket-level WORM lock duration 399 will expire for that job and corresponding secondary copies 116, i.e., date of creation+WORM lock duration. Column 534 indicates when the copy retention period 501 is met after the corresponding DDB is sealed. Column 536 indicates when the jobs/copies associated with the respective DDB become eligible to be pruned, which in this case is as soon as the secondary copies satisfy retention period 501 after sealing the DDB and the WORM lock is released on the respective volume folder 182.

Thus, according to this example, DDB1 is sealed on day 30 and the copy retention period 501 expires for the day-30 job on day 60 (column 534). Thus, after day 60, all the jobs and deduplicated secondary copies associated with DDB1 have met the established retention interval and are past their useful life (column 534). However, because of the bucket-level WORM lock that applies here, the storage platform 350 keeps them around longer based on their creation date. On day 61, the WORM lock is released on the day-1 job/copies (in volume vol1) and accordingly, system 300 initiates a pruning job for volt On day 62, the WORM lock is released on the day-2 job/copies (in volume vol2) and accordingly, system 300 initiates a pruning job for vol2. And so on, until the WORM lock is released on the last of the DDB1-related volumes (vol30) on day 90, at which time system 300 initiates a pruning job for vol30. This day-by-day approach, in contrast to what is shown in FIG. 5A, shortens the average time that data resides on storage platform 350 to 60 days, because each day's jobs/copies need not linger in storage past 60 days from being stored thereon. Media agent 345 illustratively performs the pruning jobs.

FIG. 5C depicts object-level WORM handling of deduplicated secondary copies in system 300, according to an illustrative embodiment. The scenarios depicted here correspond to FIGS. 4A and 4B, i.e., enhanced data storage management of object-level WORM-enabled storage. The backup retention period 501 and the DDB seal frequency 502 are the same 30 days each as in FIGS. 5A and 5B. However, the WORM expiry time 499 is fixed, which means that the WORM lock duration 550 for each object (e.g., volume folder, chunk folder, file, etc.) is variable. Columns 510-516, 530, 534, and 522 represent the same kind of information as those depicted in FIGS. 5A and/or 5B. Column 552 corresponds to the WORM expiry time 499, i.e., the time when storage platform 350 releases the WORM lock on the data object(s) of the corresponding deduplication copy job. The copy retention period 501 is 30 days, which can be met after DDB1 is sealed at day 30, thus amounting to 60 days after the first job and 30 days after the last job associated with DDB1. Column 554 indicates the day of WORM lock expiry.

In this timetable, all secondary copies 116 associated with DDB1 are eligible for pruning on day 60, which meets the 30-day copy retention interval of 30 days after the DDB is sealed. This object-level approach, in contrast to what is shown in FIG. 5B, shortens the average time that secondary copies reside on storage platform 350 to a range of 30-60 days, resulting in an average stay of ½(30+60)=45 days. This is substantially less than the 60-day average stay depicted in FIG. 5B and even less than the 75-day average stay depicted in the prior art of FIG. 5A. Preferably, one pruning job is initiated for all the data objects/secondary copies associated with DDB1. Media agent 345 illustratively performs the pruning.

The examples given in FIGS. 5A-5C use certain time parameters as examples to help the reader's understanding of the present disclosure, but the invention is not so limited. In other embodiments, different time parameters may be chosen, e.g., 60 days retention period 501, etc. Because the amount of storage needed to accommodate the different scenarios will vary based on the average duration that secondary copies 116 spend on storage platform 350, as exemplified in FIGS. 5A-5C, data owners will incur corresponding storage costs, particularly for cloud-based storage. Therefore, data owners may choose different retention periods than the ones shown in the examples herein to balance cost objectives and data retention preferences.

FIG. 6 depicts some salient operations of a method 600 according to an illustrative embodiment. Method 600 is performed by one or more components of system 300, unless otherwise noted. At block 602, system 300 provides and operates a native user interface for WORM configuration options to be used for deduplicated secondary copies generated by the system. The native user interface provides users (e.g., system administrators, owners, operators, etc.) with features enabling users to indicate that deduplicated secondary copies 116 are to be stored in a WORM-enabled storage target such as storage platform 350/450. This will drive not only WORM-related locking and retention, but will also drive how and when the WORM-released copies 116 are pruned. See also FIGS. 7 and 14 for additional details. At block 604, system 300 causes WORM-enabled storage resources (e.g., a storage bucket) at storage platform 350/450 to be configured according to configuration options determined at block 602. For example, system 300 may use an API or other protocol to set WORM lock parameters at storage platform 350/450. See also FIG. 8 for more details. At block 606B/606O, system 300 runs deduplication copy jobs to generate deduplicated secondary copies 116. Bucket-level WORM handling in block 606B(bucket) is discussed in further detail in FIG. 9 . Object-level WORM handling in block 6060O(object) is discussed in further detail in FIG. 10 . When it is time to seal the currently active DDB, control passes to block 608. At block 608, system 300 seals the currently active DDB 346 and performs associated operations, after which control passes back to block 606B or 606O to continue running deduplication copy jobs. More details are given in FIG. 11 . At block 610, system 300 initiates pruning of aged-off deduplicated secondary copies, i.e., copies 116 that are eligible for pruning. As shown in FIGS. 5B and 5C, the scope or granularity of pruning depends on which WORM model is used (e.g., bucket versus object). More details are given in FIG. 12 .

FIG. 7 depicts some salient operations of block 602 in method 600 according to an illustrative embodiment. Block 602 is generally directed to system 300's native user interface for configuring WORM options for deduplicated secondary copies 116 generated by the system. Storage manager 340 comprises user interface logic 1302, which presents an enhanced user interface and which also performs certain processing functions relating to WORM parameters. Thus, the features described in the present figures are accessible to users via the enhanced user interface and are processed by storage manager 340 using (at least in part) user interface logic 1302. More details are given in FIG. 13 . At block 702, system 300 (e.g., using user interface logic 1302 at storage manager 340) initiates configuration of a storage policy (e.g., 148) for protecting primary data 112 of a primary data source. Accordingly, a subclient comprising primary data 112 is defined and a storage policy is created for protecting it. Storage policies are stored in management database 1346. One or more storage pools that act as the storage destination for deduplicated secondary copies 116 are also specified in the storage policy or in an associated operation. A storage pool comprises a bucket configured at storage platform 350/450. Many cloud service providers use the term “bucket” as their repository unit for organizing object storage, e.g., IBM Cloud Object Storage, Amazon Web Service Simple Storage Service (AWS S3), Google Cloud Storage, etc. This term will be used herein as a convenient shorthand regardless of whether storage platform 350/450 is cloud-based or non-cloud. Thus, in the present disclosure, “bucket” is a term for storage resources at storage platform 350/450. At block 704, system 300 (e.g., using user interface logic 1302 at storage manager 340) provides an option to save deduplicated copies at a WORM-enabled cloud storage platform, e.g., 350, 450. One example implementation is that a user may select “mark archive files as read-only” when selecting a destination storage library for deduplicated secondary copies 116. See, e.g., the example screenshot in FIG. 14 , without limitation.

At block 706, system 300 (e.g., using user interface logic 1302 at storage manager 340) configures a retention period 501 for secondary copies 116, e.g., 30 days. According to some embodiments, retention period 501 forms the basis for how the other timing parameters are established for WORM governance of the deduplicated secondary copies 116. At block 708, system 300 (e.g., using storage manager 340) configures a sealing frequency 502 for the active deduplication database (DDB). Preferably, DDB seal frequency 502 equals the copy retention period 501 set up at block 706, in order to maintain a regular pruning cadence, but the invention is not so limited. Preferably, the DDB seal frequency 502 is automatically set by storage manager 340 (e.g., by user interface logic 1302, by DDB sealing logic 1310, etc.) after the retention period 501 is established at block 706.

FIG. 8 depicts some salient operations of block 604 in method 600 according to an illustrative embodiment. Block 604 is generally directed at causing WORM storage resources at storage platform 350/450 to be configured according to configuration options established natively in system 300, i.e., implementing administrative choices made at system 300 into configuration settings at storage platform 350/450. System 300 implements somewhat different approaches depending on whether the chosen storage platform is object-level or bucket-level WORM-enabled. At block 802, system 300 determines whether a selected storage platform is object-level or bucket-level enabled, based on one or more of: an entry made by the user at the user interface, intelligence about the storage platform natively built into user interface logic 1302, a parameter or indication extracted (e.g., by media agent 344) from the storage platform, or a combination thereof, without limitation. System 300 “prefers” object-level storage over bucket-level, because object-level tends to be more storage-efficient as illustrated by the examples in FIGS. 5A-5C. Accordingly, if a choice is to be made by a user, the system illustratively presents object-level as a default. For bucket-level storage, control passes to block 820; for object-level storage, control passes to block 804.

At block 804, system 300 (e.g., using media agent 344) gains access to object-level storage platform 450, e.g., via an API or equivalent protocol. Media agent 344 establishes a bucket at storage platform 450 based on instructions received from storage manager 340, e.g., after storage policies and storage pools are administered for certain subclient/primary data 112. The bucket will receive deduplicated secondary copies 116. In some embodiments, media agent 344 further configures volume folders 182, whereas in other embodiments each volume 182 is configured on demand, when a job begins generating data objects for the storage platform. At block 806, system 300 (e.g., using storage manager 340) optionally determines an amount of storage to provision in the storage platform sufficient for at least one WORM retention cycle, i.e., a “baseline” size or amount of storage needed before copies 116 can be pruned. The amount will be based on the estimated size of deduplicated secondary copies 116 generated in a deduplication copy job added up over a DDB sealing interval and relying on the average retention time described in FIG. 5C. This forms the basis for the amount of data storage to provision in the bucket of storage platform 450. However, for storage that is provisioned on demand, such as cloud-based storage, this determination is not needed. For storage arrays or other storage platforms that have a finite amount of storage, the storage bucket must be properly sized and provisioned. At block 808, system 300 (e.g., using storage manager 340) optionally instructs media agent 344 to access storage platform 450 (e.g., via API) and cause the storage bucket to be provisioned in the desired storage amount. As with block 806, this step is not needed where storage resources are available on demand. Control passes to block 828.

At block 820, system 300 (e.g., using storage manager 340) calculates a WORM lock duration 399, which is based on the copy retention period 501 and the DDB sealing frequency 502, as illustrated in FIG. 5B. For bucket-level WORM storage, the WORM lock duration 399 will be a fixed duration of time, e.g., 60 days, that storage platform 350 will apply to and enforce on every data object in the bucket. At block 821, system 300 (e.g., using media agent 344) gains access to bucket-level storage platform 350, e.g., via an API or equivalent protocol. Media agent 344 establishes a bucket at storage platform 350 and an applicable WORM lock duration 399 for it, based on instructions received from storage manager 340, e.g., after storage policies and storage pools are administered. The bucket will receive deduplicated secondary copies 116. In some embodiments, media agent 344 further configures volume folders 182 within the storage bucket, whereas in other embodiments each volume 182 is configured on demand, when a job begins generating data objects for storage platform 350. At block 822, system 300 (e.g., using storage manager 340) optionally determines an amount of storage to provision in storage platform 350 sufficient for at least one WORM retention cycle, i.e., a “baseline” size or amount of storage needed before copies 116 can be pruned. The amount will be based on the estimated size of deduplicated secondary copies 116 generated in a deduplication copy job added up over a DDB sealing interval and relying on the average stay as described in FIG. 5B. This forms the basis for the amount of data storage to provision in the bucket of storage platform 350. However, for storage that is provisioned on demand, such as cloud-based storage, this determination is not needed. For storage arrays or other storage platforms that have a finite amount of storage, the storage bucket must be properly sized and provisioned. At block 824, system 300 (e.g., using storage manager 340) optionally instructs media agent 344 to access storage platform 350 (e.g., via API) and cause the storage bucket to be provisioned in the desired storage amount. As with block 822, this step is not needed where storage resources are available on demand. Control passes to block 828.

At block 828, the initial configuration at storage platform 350/450 is implemented and complete. At this point, deduplication copy jobs may begin to run as described in FIGS. 9 and 10 , and data objects may be stored in the provisioned storage bucket.

FIG. 9 depicts some salient operations of block 606B (bucket-level WORM) in method 600 according to an illustrative embodiment. Block 606B is generally directed at system 300 running (executing, performing) deduplication copy jobs using bucket-level WORM storage. At block 902, system 300 (e.g., using storage manager 340 and/or media agent 345) initiates (creates, activates) a new DDB 346 if none is currently active; otherwise system 300 continues using the currently active DDB 346 until the DDB is sealed. An active DDB may not exist on a first-ever deduplication copy job in system 300 or if an existing DDB has been sealed. Storage manager 340 instructs media agent 345 to create a new DDB 346. In some embodiments, media agent 345 has sufficient intelligence to create the new DDB without specific instruction from storage manager 340. At block 904, system 300 (e.g., using storage manager 340) initiates a deduplication copy job based on a storage policy that governs the particular subclient, e.g., primary data 112. Accordingly, storage manager 340 instructs data agent 142 and media agent 344 to execute the job based on the parameters included in the storage policy, e.g., deduplication enabled (client-side or target-side), storage target/destination library for copies 116 is WORM-enabled, retention period 501, etc.

At block 906, system 300 (e.g., using media agent 344) creates a new volume folder object 182 in the storage bucket of storage platform 350, if no such volume folder was previously created for the present job. This volume folder 182 will house all the deduplication secondary copies 116 associated with the present deduplication copy job initiated at block 904. Accordingly, block 906 may occur before the job is initiated or substantially concurrently therewith, without limitation. In some embodiments, volume folder 182 is created on demand with the first product generated by the job, e.g., a chunk folder 184/185. Illustratively, once a volume folder object 182 is created in the storage bucket of storage platform 350, storage platform 350 applies the WORM lock e.g., duration 399, to the object and its constituent/nested objects, e.g., chunk folders 184/185, S-files 190/191/193, etc. Thus, the same WORM lock duration 399 applies to all sub-tending or nested objects within a volume folder 182.

At block 908, system 300 (e.g., using data agent 142 and media agent 344) generates deduplicated secondary copies 116 organized into chunk folders 184/185. For client-side deduplication, data agent 142 will use the currently active DDB 346 to check data block signatures (see also communication pathway 395). For target-side deduplication, media agent 344 will use the currently active DDB 346 to check data block signatures (see also communication pathway 396). See also FIG. 1H and accompanying text. At block 910, system 300 (e.g., media agent 344) stores secondary copies 116 (e.g., chunk folders 184/185) in volume folder 182 created at the storage bucket. Illustratively, all data objects generated in a given deduplicated copy job are stored into the same volume folder 182. Control passes back to block 908. At block 912, system 300 (e.g., media agent 344) detects that an inactivity interval has passed at the presently used volume folder 182, i.e., nothing new has been written or added therein for some time, and marks the volume folder 182 as “Full” or “Closed” and stops using it. Consequently, the next deduplication copy job will need a new volume folder 182. Preferably, a new volume folder 182 is created for every deduplication copy job at block 906, but the invention is not so limited. In some embodiments, a new volume folder is created on every calendar day, as in the example of FIG. 5B, and thus a volume folder 182 may comprise copies 116 from more than one deduplication copy job performed that day. Control passes back to block 904 for the next deduplication copy job.

FIG. 10 depicts some salient operations of block 606O (object-level WORM) in method 600 according to an illustrative embodiment. At block 1002, which is analogous to block 902, system 300 initiates (creates, activates) a new DDB 346 if none is currently active. If there is an active DDB, system 300 continues using the active DDB until the DDB is sealed. At block 1004, which is analogous to block 904, system 300 initiates a deduplication copy job based on a storage policy that governs the particular subclient, e.g., primary data 112.

At block 1006, system 300 (e.g., using storage manager 340, media agent 344) determines a WORM lock expiry parameter for the present job. Because the disclosed approach “macro-prunes” secondary copies 116 holistically for an entire deduplication copy job, the WORM lock expiry is preferably calculated for the job as a whole and will apply to all secondary copies 116 generated by that job. The WORM lock will be applied by storage platform 450. The WORM lock expiry is based on the retention period 501 for secondary copies and on the DDB seal frequency 502 as explained elsewhere herein. In some embodiments, the WORM lock expiry parameter is embodied as a fixed expiry time 499, e.g., midnight on December 1st. In other embodiments, the WORM lock expiry parameter is a progressively diminishing WORM lock duration 550, which is calculated anew for each job and/or object of the job, and which ends at a fixed time, 499. Different storage platforms 450 may use different ways of implementing the WORM lock expiry parameter for object-level enforcement, i.e., fixed expiry time, diminishing duration, etc., without limitation.

At block 1008, which is analogous to block 906, system 300 creates a new volume folder object) 182 in the storage bucket of storage platform 450, if no such volume folder was previously created for the present job. This volume folder 182 will house all the deduplication secondary copies 116 associated with the present deduplication copy job initiated at block 1004. Accordingly, block 1008 may occur before the job is initiated or substantially concurrently therewith, without limitation. In some embodiments, volume folder 182 is created on demand with the first data object generated by the job, e.g., a chunk folder 184/185. Once an object (e.g., volume folder 182) is created in the storage bucket of storage platform 450, storage platform 450 applies the WORM lock to the object, e.g., expiry time 499, as received from media agent 344 at block 1014.

At block 1010, which is analogous to block 908, system 300 generates deduplicated secondary copies 116, comprising chunk folder 184/185. At block 1012, which is analogous to block 910, system 300 stores secondary copies 116 (e.g., chunk folders 184/185) into volume folder 182 created at the storage bucket. Illustratively, all data objects generated in a given deduplicated copy job are stored into the same volume folder 182. Control passes back to block 1010 for the next round of copies 116. At block 1014, system 300 (e.g., using media agent 344 and an API to storage platform 450) supplies the WORM lock expiry parameter determined at block 1006 to storage platform 450. This step may be concurrent with block 1012, e.g., may be included in data transmission and/or signaling accompanying secondary copies 116. In some embodiments, the WORM lock expiry parameter is transmitted to storage platform 450 after being calculated at block 1006 and/or with the creation of volume folder 182 at block 1008, without limitation. Storage platform 450 applies the WORM lock to and enforces it upon each data object stored therein. At block 1016, which is analogous to block 912, system 300 detects that an inactivity interval has passed at the presently used volume folder 182, i.e., nothing new has been written or added therein for some time, and marks the volume folder 182 as “Full” or “Closed” and stops using it. Consequently, the next deduplication copy job will need a new volume folder 182. Control passes back to block 1004 for the next deduplication copy job.

FIG. 11 depicts some salient operations of block 608 in method 600 according to an illustrative embodiment. Block 608 is generally directed to sealing of the active DDB 346 and performing other operations based on the sealing event. At block 1102, system 300 (e.g., using storage manager 340 and/or media agent 345) monitors DDB seal frequency 502 in reference to the currently active DDB 346. In some embodiments, after sealing frequency 502 is established at block 708, storage manager 340 saves it to management database 1346, and additionally transmits it to media agent 345. Media agent 345 then monitors or tracks whether and when the active DDB should be sealed. In alternative embodiments, storage manager 340 performs the monitoring and tracking and instructs media agent 345 when to seal the currently active DDB. At block 1104, system 300 (e.g., using storage manager 340 and/or media agent 345) determines whether a time interval has been reached based the DDB sealing frequency. If not, the currently active DDB remains active and control passes back to monitoring at block 1102. If yes, control passes to block 1106.

At block 1106, system 300 (e.g., using storage manager 340 and/or media agent 345) seals the currently active DDB 346. Illustratively, media agent 345 performs the sealing. In some embodiments, it does so as instructed by storage manager 340, whereas in other embodiments it initiates the sealing based on its own determination that it is time to do so based on sealing frequency 502. Once the currently active DDB is sealed, a new DDB is created at block 606B/606O to support future deduplication copy jobs. Once a DDB is sealed, system 300 no longer directs signature lookups to it, and the sealed DDB is deactivated and withdrawn from service. At block 1108, system 300 (e.g., using storage manager 340, media agent 345) initiates pruning of sealed DDB 346. This may occur some time after the DDB is sealed, and need not occur immediately after the sealing. In some embodiments, block 1108 occurs after system 300 (e.g., media agent 345) determines that a new DDB has been successfully created at block 902/1002. In some embodiments, the sealed DDB is retained for a limited time, for example until the new DDB is sealed and yet another DDB is created. In some embodiments, storage manager 340 instructs media agent to delete the sealed DDB, whereas in other embodiments, media agent 345 controls the timing of DDB deletion. At block 1110, system 300 (e.g., using media agent 345) logically deletes the sealed DDB from system 300 (if not completed at block 1106) and deletes the sealed DDB contents from the storage devices at media agent host computing device 306.

FIG. 12 depicts some salient operations of block 610 in method 600 according to an illustrative embodiment. Block 610 is generally directed to pruning of aged-off (deletion-eligible) deduplicated secondary copies 116 from storage platform 350/450. At block 1202, system 300 (e.g., using storage manager 340 and/or media agent 344) begins the process of pruning (deleting, removing) stale deduplicated secondary copies 116, including their constituent data objects such as chunk folders 184/185, S-files 190/191/193, etc., from storage platform 350/450. Thus, for each data object, blocks 1204-1212 are executed. In some embodiments, pruning/deletion is applied to the volume folder 182 and all its constituent data objects collectively, whereas in other embodiments, each granular data object is individually operated upon, preferably substantially concurrently with other data objects having the same deletion eligibility time within volume folder 182. To cover all these possible implementations, the operations below are described in reference to a data object, without regard to its granularity.

At block 1204, system 300 (e.g., using storage manager 340 and/or media agent 344) determines whether storage platform 350/450 has released its WORM lock on a given data object. Storage platform 350/459 releases the WORM lock on the data object at such time as the WORM lock retention 399 or WORM lock expiry 499 occurs, respectively. In some embodiments, the storage platform communicates (or confirms) the WORM lock release to media agent 344 and/or the WORM lock release is affirmatively detected or discovered by media agent 344. In other embodiments, the WORM lock release is deduced or inferred by media agent 344 and/or storage manager 340 based on WORM lock parameter(s) previously submitted to the storage platform, e.g., at block 821, at block 1014, etc. On determining or concluding that the WORM lock has been released, system 300 passes control to block 1206. If there is no WORM lock release as yet, control returns to block 1202. At block 1206, system 300 (e.g., using storage manager 340 and/or media agent 344) determines or confirms that the retention period 501 for the data object has in fact expired. In some embodiments, this check is skipped, as system 300 relies on the WORM lock release to act as a proxy for meeting the data object retention criteria. If the data object remains within its retention period 501, system 300 awaits its expiration. If the data object's retention period 501 has expired, control passes to block 1208.

Block 1208 is reached when system 300 (e.g., using storage manager 340 and/or media agent 344) has determined (at block 1206) that the data object is eligible to be pruned (deleted, removed) from the storage platform. Consequently, control passes to block 1210. At block 1210, system 300 (e.g., using storage manager 340) initiates a pruning job for the data object. In some embodiments, storage manager 340 instructs media agent 344 to delete the data object. At block 1212, system 300 (e.g., using media agent 344) causes the data object to be deleted from the storage platform. In some embodiments, media agent 344 accomplishes this task by communicating delete instructions (e.g., via API) to the storage platform. The media agent 344 need not cause or implement the deletion immediately. To optimize computing resources at media agent host computing device 106, media agent 344 may proceed with the pruning job when other (possibly higher priority) tasks are completed, e.g., secondary copy jobs, restore jobs, etc. Thus, storage manager 340 and/or media agent 344 may assign a lower priority to the present task, allowing media agent 344 to perform the pruning at a convenient time and not necessarily when the pruning job is initiated by storage manager 340. Once the data object is deleted from the storage platform, the data object's storage space is released and may be re-used by the storage platform. In pay-as-you-go configurations, such as cloud storage services, releasing the storage space saves the customer the cost of storing the data object at the storage platform. Control passes back to block 1202 for the next data object.

FIG. 13 is a block diagram illustrating some functional components of and/or associated with storage manager 340 in system 300, according to an illustrative embodiment. The present figure depicts: data agent 142; media agent 344; storage manager 340 comprising user interface logic 1302, jobs agent 1308, DDB sealing logic 1310, volume management logic 1312, purge management logic 1314, and management database 1346 comprising policies 1304 and schedules 1306; web server 1350 hosting Command Center; and computing device 1352. User interface logic 1302 (or “WORM configuration user interface logic”) is a functional component of storage manager 340, which particularly supports configuring WORM-related features and parameters, in a manner native to system 300, with an enhanced user interface of system 300. The user interface is presented to users as a graphical user interface via a web server 1350 as the so-called “Command Center.” The user interface also takes a more traditional form as a “Java GUI” that bypasses the web server and which is also supported by user interface logic 1302. The features described in the present figures are accessible to users via the user interface and are processed by storage manager 340 using (at least in part) user interface logic 1302. See also FIG. 7 , FIG. 8 , and FIG. 14 . User interface logic 1302 is configured to receive a copy retention duration 501, establish a DDB sealing frequency 502, calculate WORM-related expiry time parameters, such as 399, 499, etc., and additionally is responsible for storing such WORM-related parameters in management database 1346.

Jobs agent 1308 is a functional component of storage manager 340, and in some embodiments is an enhanced version of jobs agent 156. Like jobs agent 156, jobs agent 1308 initiates, controls, and/or monitors deduplication copy jobs, pruning jobs, DDB sealing jobs, etc., without limitation. Like jobs agent 156, jobs agent 1308 gains access to storage policies 148 (e.g., in management database 1346) to determine when, where, and how to initiate/control jobs in system 300, including deduplication copy jobs that make use of WORM-enabled storage. DDB sealing logic 1310 is a functional component of storage manager 340. DDB sealing logic 1310 illustratively determines a proper DDB seal frequency 502 and/or obtains frequency 502 from user interface logic 1302. DDB sealing logic 1310 interoperates with media agent 345 to enable performance of the tasks described in FIG. 11 , without limitation. Volume management logic 1312 is a functional component of storage manager 340. Volume management logic 1312 illustratively controls the creation and closing of volume folders 182 used in deduplication copy jobs. Volume management logic 1312 interoperates with media agent 344. See, e.g., blocks 906, 912, 1008, 1016, without limitation. Purge management logic 1314 is a functional component of storage manager 340. Purge management logic 1314 illustratively controls when data objects such as volume folders 182 become eligible for deletion and then initiates purge jobs. Purge management logic 1314 interoperates with media agent 344 enable performance of the tasks described in FIG. 12 , without limitation.

Management database 1346 is analogous to management database 146 and additionally comprises information, tables, and/or other data structures in support of WORM-storage management at system 300. Management database 1346 is a logical, but not necessarily a physical part, of storage manager 340 and computing device 304. Storage policies 1304 and schedules 1306 are stored in management database 1346. WORM-related configuration parameters, e.g., 399, 499, 501, 502, 503, 550, etc., without limitation, are stored, updated, and maintained in management database 1346. Storage policies 1304 and schedules (or schedule policies) 1306 are analogous to policies 148, and are particularly configured to govern how primary data 112 is protected with deduplication in WORM-enabled storage platforms.

Web server 1350 is a web-based computing device or computing resource that comprises one or more hardware processors. Web server 1350 hosts the Command Center user interface, which is a web-based user interface for data storage management system 300. Command Center, as well as its non-web counterpart, the Java GUI, is used for configuration data entry and administration tasks, and for obtaining reports, alarms, and/or dashboards from and about system 300. Web server 1350 presents the Command Center user interface to computing device 1352. Computing device 1352, which is well known in the art, is a computing device comprising hardware processors, which is used for gaining access to web server 1350 and from there to storage manager 340.

The functional components depicted in the present figure that are part of storage manager 340 are shown here as distinct functional logic components to ease the reader's understanding of the present disclosure and to highlight some of the new features added to storage manager 340, but the invention is not limited to this implementation. In other embodiments, one or more or all of these logic components are integrated with or layered within other parts of storage manager code and are not necessarily separate or distinct. Moreover, the user interface logic 1302 is not limited to the examples given herein in regard to optionable choices presented to users. In other embodiments, the user interface may be differently arranged and presented than the examples given herein.

FIG. 14 depicts example screenshot segments from the native user interface presented by system 300. This figure depicts an example portion of an administration screen of system 300 presented by the Command Center user interface. Here, the destination storage at storage platform 350/450 (the so-called “library’) has an associated option that the user may select or check off: “Mark Archive files as Read-Only.” The example screen adds that “When this option is selected, the system creates archive files in the disk library with read-only permissions.” This option corresponds to choosing WORM protection for the secondary copies 116 being stored into the storage platform. As noted, this screenshot is included here as an example, not as a limitation. In other embodiments, “Mark Archive files as Read-only” is replaced by “WORM Storage” for the library, to more clearly enunciate the use of WORM-enabled storage for secondary copies.

In regard to the figures described herein, other embodiments are possible within the scope of the present invention, such that the above-recited components, steps, blocks, operations, messages, requests, queries, and/or instructions are differently arranged, sequenced, sub-divided, organized, and/or combined. In some embodiments, a different component may initiate or execute a given operation. In some embodiments, multiple components may interoperate to execute a plurality of depicted operations substantially concurrently in order to perform the disclosed feature(s).

EXAMPLE EMBODIMENTS

Some example enumerated embodiments of the present invention are recited in this section in the form of methods, systems, and non-transitory computer-readable media, without limitation.

According to an example embodiment, a data storage management system comprises: a first computing device hosting a storage manager, wherein the first computing device comprises one or more hardware processors and computer memory, and wherein the first computing device is configured to: provide a user interface for administering a storage policy comprising one or more write-once read-many (WORM) options for deduplicated secondary copies generated by the system; cause a storage bucket at a WORM-enabled storage platform to be configured according to the one or more WORM options administered via the user interface; execute a plurality of secondary copy jobs associated with a first deduplication database (DDB), wherein a second plurality of deduplicated secondary copies, which result from the plurality of secondary copy jobs, are stored into the storage bucket; seal the first DDB based on passing a sealing interval; and based on the first DDB having been sealed, and further based on the storage platform releasing a WORM lock on at least one of the deduplicated secondary copies, initiate pruning of the at least one of the deduplicated secondary copies from the storage bucket.

The above-recited embodiment, wherein the storage platform provides bucket-level WORM-enabled storage at the storage bucket, and wherein a WORM lock duration applies to each deduplicated secondary copy stored therein and wherein the WORM lock duration starts when a respective deduplicated secondary copy is stored in the storage bucket. The above-recited embodiment, wherein the WORM lock duration comprises a sum of the sealing interval and a retention period for deduplicated secondary copies, which is received via the user interface. The above-recited embodiment, wherein the respective deduplicated secondary copy is eligible for pruning based on the first DDB having been sealed, and further based on the retention period, which is set in a storage policy administered via the user interface, and further based on the WORM lock having been released by the storage platform. The above-recited embodiment, wherein the storage platform provides object-level WORM-enabled storage at the storage bucket, and wherein a WORM expiration parameter expires at a fixed time and applies to each of the second plurality of deduplicated secondary copies in the storage bucket The above-recited embodiment, wherein the WORM expiration parameter is based on a sum of the sealing interval and a retention period for deduplicated secondary copies. The above-recited embodiment, wherein a respective deduplicated secondary copy is eligible for pruning based on the first DDB having been sealed, and further based on the retention period, which is set in a storage policy administered via the user interface, and further based on the WORM lock having been released by the storage platform at the fixed time. The above-recited embodiment, wherein the WORM expiration parameter expires when a sum of the sealing interval and a retention period for deduplicated secondary copies expires. The above-recited embodiment, wherein the pruning is initiated collectively for all of the second plurality of deduplicated secondary copies. The above-recited embodiment, further comprising: a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory, and wherein the second computing device is configured to: receive from the first computing device the one or more WORM options administered via the user interface; and communicate electronically with the storage platform and instruct the storage platform to implement the storage bucket according to the one or more WORM options. The above-recited embodiment, further comprising: a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory, and wherein the second computing device is configured to: activate the first DDB at the second computing device; seal the first DDB as instructed by the first computing device; prune the first DDB from the second computing device; and activate a second DDB at the second computing device.

According to another example embodiment, a computer-implemented method comprises: by a first computing device hosting a storage manager, wherein the first computing device comprises one or more hardware processors and computer memory: providing a user interface for administering a storage policy comprising one or more write-once read-many (WORM) options for storing deduplicated secondary copies generated by a data storage management system from a source of primary data; causing a storage bucket at a WORM-enabled storage platform to be configured according to the One or more WORM options administered via the user interface; executing a first plurality of deduplication copy jobs based on using a first deduplication database (DDB), wherein a second plurality of deduplicated secondary copies, which result from the first plurality of deduplication copy jobs, are stored into the storage bucket; sealing the first DDB based on a DDB sealing frequency; and based on the first DDB having been sealed, and further based on the storage platform releasing a WORM lock on at least one of the deduplicated secondary copies, initiate pruning of the at least one of the deduplicated secondary copies from the storage bucket.

The above-recited embodiment, wherein the storage platform provides bucket-level WORM-enabled storage at the storage bucket, and wherein a WORM lock duration applies to each deduplicated secondary copy stored therein and wherein the WORM lock duration starts when a respective deduplicated secondary copy is stored in the storage bucket. The above-recited embodiment, wherein the WORM lock duration comprises a sum of the DDB sealing frequency and a retention period for deduplicated secondary copies, which is received via the user interface. The above-recited embodiment, wherein the respective deduplicated secondary copy is eligible for pruning based on the first DDB having been sealed, and further based on the retention period, which is set in a storage policy administered via the user interface, and further based on the WORM lock having been released by the storage platform. The above-recited embodiment, wherein the storage platform provides object-level WORM-enabled storage at the storage bucket, and wherein a WORM expiration parameter expires at a fixed time and applies to each of the second plurality of deduplicated secondary copies in the storage bucket. The above-recited embodiment, wherein the WORM expiration parameter is based on a sum of the DDB sealing frequency and a retention period for deduplicated secondary copies. The above-recited embodiment, wherein a respective deduplicated secondary copy is eligible for pruning based on the first DDB having been sealed, and further based on the retention period, which is set in a storage policy administered via the user interface, and further based on the WORM lock having been released by the storage platform at the fixed time. The above-recited embodiment, wherein the WORM expiration parameter expires when a sum of the DDB sealing frequency and a retention period for deduplicated secondary copies expires. The above-recited embodiment, wherein the pruning is initiated collectively for all of the second plurality of deduplicated secondary copies. The above-recited embodiment, further comprising: by a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory: receiving from the first computing device the one or more WORM options administered via the user interface; and communicating electronically with the storage platform and instructing the storage platform to implement the storage bucket according to the one or more WORM options. The above-recited embodiment, further comprising: by a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory: activating the first DDB at the second computing device; sealing the first DDB as instructed by the first computing device; pruning the first DDB from the second computing device; and activating a second DDB at the second computing device.

In other embodiments according to the present invention, a system or systems operates according to one or more of the methods and/or computer-readable media recited in the preceding paragraphs. In yet other embodiments, a method or methods operates according to one or more of the systems and/or computer-readable media recited in the preceding paragraphs. In yet more embodiments, a non-transitory computer-readable medium or media causes one or more computing devices having one or more processors and computer-readable memory to operate according to one or more of the systems and/or methods recited in the preceding paragraphs.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense, i.e., in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words using the singular or plural number may also include the plural or singular number respectively. The word “or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list. Likewise the term “and/or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list.

In some embodiments, certain operations, acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all are necessary for the practice of the algorithms). In certain embodiments, operations, acts, functions, or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described. Software and other modules may reside and execute on servers, workstations, personal computers, computerized tablets, PDAs, and other computing devices suitable for the purposes described herein. Software and other modules may be accessible via local computer memory, via a network, via a browser, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, interactive voice response, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. Two or more components of a system can be combined into fewer components. Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems and/or computing devices. Likewise, the data repositories shown can represent physical and/or logical data storage, including, e.g., storage area networks or other distributed storage systems. Moreover, in some embodiments the connections between the components shown represent possible paths of data flow, rather than actual connections between hardware. While some examples of possible connections are shown, any of the subset of the components shown can communicate with any other subset of components in various implementations.

Embodiments are also described above with reference to flow chart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products. Each block of the flow chart illustrations and/or block diagrams, and combinations of blocks in the flow chart illustrations and/or block diagrams, may be implemented by computer program instructions. Such instructions may be provided to a processor of a general purpose computer, special purpose computer, specially-equipped computer (e.g., comprising a high-performance database server, a graphics subsystem, etc.) or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor(s) of the computer or other programmable data processing apparatus, create means for implementing the acts specified in the flow chart and/or block diagram block or blocks. These computer program instructions may also be stored in a non-transitory computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the acts specified in the flow chart and/or block diagram block or blocks. The computer program instructions may also be loaded to a computing device or other programmable data processing apparatus to cause operations to be performed on the computing device or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computing device or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention. These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.

To reduce the number of claims, certain aspects of the invention are presented below in certain claim forms, but the applicant contemplates other aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as a means-plus-function claim under 35 U.S.C. sec. 112(f) (AIA), other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. Any claims intended to be treated under 35 U.S.C. § 112(f) will begin with the words “means for,” but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly, the applicant reserves the right to pursue additional claims after filing this application, in either this application or in a continuing application. 

What is claimed is:
 1. A data storage management system comprising: a first computing device hosting a storage manager, wherein the first computing device comprises one or more hardware processors and computer memory, and wherein the first computing device is configured to: provide a user interface for administering a storage policy comprising one or more write-once read-many (WORM) options for deduplicated secondary copies generated by the data storage management system; cause a storage bucket at a storage platform, which is WORM-enabled, to be configured according to the one or more WORM options administered via the user interface; execute a plurality of secondary copy jobs associated with a first deduplication database (DDB), wherein a second plurality of deduplicated secondary copies, which result from the plurality of secondary copy jobs, are stored into the storage bucket; seal the first DDB based on passing a sealing interval; and based on the first DDB having been sealed, and further based on the storage platform releasing a WORM lock on at least one of the deduplicated secondary copies, initiate pruning of the at least one of the deduplicated secondary copies from the storage bucket.
 2. The data storage management system of claim 1, wherein the storage platform provides bucket-level WORM-enabled storage at the storage bucket, and wherein a WORM lock duration applies to each deduplicated secondary copy stored therein and wherein the WORM lock duration starts when a respective deduplicated secondary copy is stored in the storage bucket.
 3. The data storage management system of claim 2, wherein the WORM lock duration comprises a sum of the sealing interval and a retention period for deduplicated secondary copies, which is received via the user interface.
 4. The data storage management system of claim 3, wherein the respective deduplicated secondary copy is eligible for pruning based on the first DDB having been sealed, and further based on the retention period, which is set in a storage policy administered via the user interface, and further based on the WORM lock having been released by the storage platform.
 5. The data storage management system of claim 1, wherein the storage platform provides object-level WORM-enabled storage at the storage bucket, and wherein a WORM expiration parameter expires at a fixed time and applies to each of the second plurality of deduplicated secondary copies in the storage bucket.
 6. The data storage management system of claim 5, wherein the WORM expiration parameter is based on a sum of the sealing interval and a retention period for deduplicated secondary copies.
 7. The data storage management system of claim 6, wherein a respective deduplicated secondary copy is eligible for pruning based on the first DDB having been sealed, and further based on the retention period, which is set in a storage policy administered via the user interface, and further based on the WORM lock having been released by the storage platform at the fixed time.
 8. The data storage management system of claim 5, wherein the WORM expiration parameter expires when a sum of the sealing interval and a retention period for deduplicated secondary copies expires.
 9. The data storage management system of claim 5 wherein the pruning is initiated collectively for all of the second plurality of deduplicated secondary copies.
 10. The data storage management system of claim 1 further comprising: a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory, and wherein the second computing device is configured to: receive from the first computing device the one or more WORM options administered via the user interface; and communicate electronically with the storage platform and instruct the storage platform to implement the storage bucket according to the one or more WORM options.
 11. The data storage management system of claim 1, further comprising: a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory, and wherein the second computing device is configured to: activate the first DDB at the second computing device; seal the first DDB as instructed by the first computing device; prune the first DDB from the second computing device; and activate a second DDB at the second computing device.
 12. A computer-implemented method comprising: by a first computing device hosting a storage manager, wherein the first computing device comprises one or more hardware processors and computer memory: providing a user interface for administering a storage policy comprising one or more write-once read-many (WORM) options for storing deduplicated secondary copies generated by a data storage management system from a source of primary data; causing a storage bucket at a storage platform, which is WORM-enabled, to be configured according to the one or more WORM options administered via the user interface; executing a first plurality of deduplication copy jobs based on using a first deduplication database (DDB), wherein a second plurality of deduplicated secondary copies, which result from the first plurality of deduplication copy jobs, are stored into the storage bucket; sealing the first DDB based on a DDB sealing frequency; and based on the first DDB having been sealed, and further based on the storage platform releasing a WORM lock on at least one of the deduplicated secondary copies, initiate pruning of the at least one of the deduplicated secondary copies from the storage bucket.
 13. The computer-implemented method of claim 12, wherein the storage platform provides bucket-level WORM-enabled storage at the storage bucket, and wherein a WORM lock duration applies to each deduplicated secondary copy stored therein and wherein the WORM lock duration starts when a respective deduplicated secondary copy is stored in the storage bucket.
 14. The computer-implemented method of claim 13, wherein the WORM lock duration comprises a sum of the DDB sealing frequency and a retention period for deduplicated secondary copies, which is received via the user interface.
 15. The computer-implemented method of claim 14, wherein the respective deduplicated secondary copy is eligible for pruning based on the first DDB having been sealed, and further based on the retention period, which is set in a storage policy administered via the user interface, and further based on the WORM lock having been released by the storage platform.
 16. The computer-implemented method of claim 12, wherein the storage platform provides object-level WORM-enabled storage at the storage bucket, and wherein a WORM expiration parameter expires at a fixed time and applies to each of the second plurality of deduplicated secondary copies in the storage bucket.
 17. The computer-implemented method of claim 16, wherein the WORM expiration parameter expires when a sum of the DDB sealing frequency and a retention period for deduplicated secondary copies expires.
 18. The computer-implemented method of claim 16, wherein the pruning is initiated collectively for all of the second plurality of deduplicated secondary copies.
 19. The computer-implemented method of claim 12 further comprising: by a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory: receiving from the first computing device the one or more WORM options administered via the user interface; and communicating electronically with the storage platform and instructing the storage platform to implement the storage bucket according to the one or more WORM options.
 20. The computer-implemented method of claim 12, further comprising: by a second computing device hosting a media agent, wherein the second computing device comprises one or more hardware processors and computer memory: activating the first DDB at the second computing device; sealing the first DDB as instructed by the first computing device; pruning the first DDB from the second computing device; and activating a second DDB at the second computing device. 